[tools] Thoughts on comps.xml processing.

[Dave]

Ray Van Dolson wrote:
> 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.

Surely that's a per-distro rather than per-repo setting? Speaking
personally I'm another user that requires a per-repo setting, as I'm
currently manually symlinking (repo)-comps.xml files under /var/mrepo.

I know that for newer releases of centos/fedora (centos4/5, fedora
7,8,9, not checked <7) the location of the comps file can be determined
by examining the group data contained in repodata/repomd.xml for each
repository in turn.

-- 
Dave