Easier way to maintain comps.xml ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all!

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?

CU
thl

--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers

--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly

[Index of Archives]     [Fedora Users]     [Fedora Development]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux