On Tue, Jun 03, 2008 at 08:29:19AM +0200, Raphael Hertzog wrote: > On Mon, 02 Jun 2008, Vagrant Cascadian wrote: > > you could also work around it by using --build-profiles, which are > > profiles only used for CD generation. > > I wrote a work-around which checks the log of the simple-cdd run instead. > The packages listed in *.downloads are installed by d-i in some specific > conditions and hence I didn't want to include them in the *.packages > files but I want to make sure they end up on the CD.
and that is *exactly* what using build-profiles will do. if you add to profiles/FOO.packages and add --build-profile FOO (and not include FOO as a regular profile), it will ensure that those packages are on the CD, but not include them when installing. you can sort of think of a build profile as a fake profile that only changes the CD building process, and thus what gets included on the CD, but shouldn't change what gets installed. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
