Easier way to maintain comps.xml ?

[Thorsten Leemhuis]

On 05.06.2007 20:53, Jesse Keating wrote:
> On Tuesday 05 June 2007 14:53:59 Thorsten Leemhuis wrote:
>> Just fishing for opinions here.
>>
>> EPEL will likely have a comps.xml soon, too. Thus if you add a new
>> package to Fedora and build it for all supported dists you have to add
>> the entry to five comps.xml files in the future (Fedora current, Fedora
>> current-1, Fedora devel, EPEL4 and EPEL5 (not counting Fedora current-2,
>> which would be FC-5 currently, but that is EOL soon)).
>>
>> Isn't there a easier way to maintain that information in the long term?
>> Maybe via the package database? The only thing that might be different
>> in the different comps.xml files is afaics the group a package belongs to.
>>
>> Or do we simply don't care as we have bigger problems right now?
> 
> We know that comps sucks, and we want to fix it.  Time and bandwidth are the 
> issues.

Ohh, sorry, I didn't know there were bigger plans on the horizon. The
it's likely the easiest to just create comps.xml for EPEL and forget
about the "package db integration" idea for now.

Thanks Jesse.

CU
knurd