>From: Jeroen van Meeuwen [mailto:kanarip@xxxxxxxxxxx] >Sent: 29 July 2009 06:55 > >On 07/28/2009 06:23 AM, Jesse Keating wrote: >> On Mon, 2009-07-27 at 15:37 -1000, David Cantrell wrote: >>> Based on notting's comment about removing the lib packages from >PACKAGES, I >>> thought we should be able to let upd-instroot do 'yum install anaconda' >and >>> get the tree we need. So I looked at what yum install anaconda would >pull >>> in at first, then moved remaining things that are listed in KEEPFILE* >lists >>> to Requires: tags in the spec file. >>> >>> This can also make life easier for lorax, as we could rely on 'yum >install >>> anaconda' to set up our tree more or less with the files we need. >> >> My gripe with this is that it makes people have to download/install >> these packages twice. Once to get anaconda on the system in order to >> run the scripts, or pungi, and then once again to create the mini chroot >> that anaconda uses to stage stuff in before putting things in yet a >> different chroot. The second install doesn't use the same caching as >> the first install, so you wind up downloading things multiple times. >> >> I don't know a good way around this :/ >> > >One way around this is a comps group just like buildsys-build. I lack a >good name idea for such group, but it solves package side of the problem. > >For the now file based requirements though... Not even sure if KEEPFILE* >was used for downloading additional stuff from the yum repos. > >-- Jeroen > Oh, THAT's how buildsys-build is supposed to work! I develop custom CentOS spins for our organisation. I've just been modifying our package list for anaconda in CentOS 5.3, so I've been following this thread with interest. I was all set to reply about how annoying the buildsys-build rpm package is in the CentOS world, but some extra poking around in the Fedora repos showed me it _is_ a proper yum group, and _is_ easy to set up and maintain. The <uservisible>false</uservisible> fooled me for a while, but I got there in the end. I would vote for an 'anaconda-inst' group along the same lines. Easy to maintain (especially if it's documented somewhere ;-) ) and no need for extra packages installed on your build server. Moray. "To err is human. To purr, feline" _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
