On Wed, 21 Nov 2007 19:55:01 +0100 Nicolas Mailhot <nicolas.mailhot@xxxxxxxxxxx> wrote: > And I'd probably curse Fedora developers for designing a system where > comps groups are an all-or-nothing thing, and you can not define a set > of profiles that reuse common elements. > > (You can of course fork the same root comps, that's how spins work, > and then you get comps sync maintenance nightmare) What are you talking about? Exactly one comps is used for all the spins. We use a manifest in a kickstart file to select which groups, packages, or excludes to use against that comps and the Everything repo to decide what goes into a spin. You can even specify if you want just the mandatory, mandatory + defaults, or even mandatory + all optional packages. Hell you can even break out the individual packages and list just a few mandatory for a group and that group option will still show up, you'll only get what's available in the repo for that group. So please, maybe I misunderstood you, but how is comps all-or-nothing? -- Jesse Keating Fedora -- All my bits are free, are yours?
Attachment:
signature.asc
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
