On Mon, 14 May 2007 11:13:34 -0400, Jesse Keating wrote:
On Monday 14 May 2007 11:03:00 Jeremy Katz wrote:
> [1] It looks like the idea is to be able to store the comps info
> directly in the buildsys so that a comps file could then just be spit
> out. But I'm not 100% sure there. And it raises some questions on how
> it works with other parts of the process around comps like translations
Not quite right. The comps thing is somewhat of a historical thing with how
mock populates the default buildroot. We've created the idea of groups
within koji, like the 'build' group, that is used to populate the buildroot.
Koji could have the ability to 'import' a written out comps file to get the
grouping information, however I've just been doing it by hand since the group
is fairly small. It has nothing to do with the comps used for composing a
distribution.
Well, I used the patched koji to import the package-set for the minimal
buildroot, which was a requirement for getting a first test-build done.