On Wed, 2008-09-10 at 17:41 +0100, Richard Hughes wrote: > On Wed, 2008-09-10 at 18:02 +0200, Nicolas Mailhot wrote: > > Please work with the anaconda team so whatever resource list format you > > end up is shared and we don't have pk catalogs vs comps files. > > I think they are two different formats for two different use cases. > > > Really our comps file is nothing but the initial catalog restricted to the > > initial repository and it's quite disturbing they have ovelapping > > functionnality with different featuresets, syntax and limitations. > > Comps has optional packages, groups, and quite a complex format. Could > you write a comps file from memory without copying an existing one and > modifying it? yes. > Right, I guess that's another key distinction. Users write catalog > files. Users don't usually enjoy writing XML, unless they are sadist > programmer types. I also don't intend on having super complex catalog > files, so that don't need to scale. Typically they will be a three lines > long at most. which is why we have a tool to create that xml file in yum-utils: yum-groups-manager.py -sv -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
