On Mon, 2008-04-21 at 13:44 +0200, Jeroen van Meeuwen wrote:
Or were you thinking something else?
I was. buildinstall recently changed how it works. You no longer point it at a directory of packages, you point it at a yum repo. You can also have it output to a different directory. So my plan, which will take some modification to createrepo (Seth is already aware of this and has it planned), is to use pungi to wire up all the repos configured in the kickstart file and generate a "reference" repo. This repo would be "local" to the file system, use a combined comps grouping (for all the repos that you wish to consider for groupdata (another change coming for pykickstart)), but the repodata itself would have hrefs to the packages locations in the other repos. You get local repodata without having to mirror all the packages. Buildinstall would be pointed at that repo, and it would download (insert caching dances here) the packages it needs in order to make install images. Then (well, still not sure of the step orders) pungi would use it's manifest to create the package trees and insert the produced images into the trees.
That's the fairly rough overview.