[tools] Thoughts on comps.xml processing.

Ray Van Dolson rvandolson at esri.com
Sun Oct 12 10:01:10 CEST 2008


So I've been trying to think on a solution to the comps.xml handling
issues still present in mrepo as of 0.8.6.  The problem being that the
code currently looks for comps.xml only in disc1/*/base/ and in
versions of RHEL and CentOS newer than 5 as well as recent Fedora's the
location name of the comps.xml file has changed (Fedora has it now as
Fedora-9-comps.xml).

Probably the closest thing I've seen to a solution was posted here:

  http://lists.rpmforge.net/pipermail/tools/2007-May/000841.html

This patch actually searches for all comps*.xml files and picks the
largest as the base.

I'm thinking something along the lines of this still makes sense, but
perhaps providing a per-repo configuration option that lets the user
specify a relative path (under disc1) to their comps.xml file might
also make sense?

Something like:

[fedora9]
comps = repodata/Fedora-9-comps.xml

Any thoughts on this?  The current workaround is to just copy the comps
file manually to os-comps.xml.

Thanks,
Ray


More information about the tools mailing list