http://fedoraproject.org/extras/4/i386/repodata/

[seth vidal]

On Sat, 2005-07-09 at 16:05 +0200, Andreas Thienemann wrote:
> On Sat, 9 Jul 2005, Konstantin Ryabitsev wrote:
> 
> > > And I consider it much better then __nogroup__.
> > It doesn't have to be. It's only a matter of inclusion into comps.xml.
> > I think part of the new package submission process, in addition to
> > "make bugzilla entry" should be "suggest group placements."
> Great. That fixes things for extras.
> 
> But what if one uses repoview to catalog third party repositories?
> The possibility not to group by comps.xml catalog but by RPM group might 
> be very appreciated.
>  
> > It makes a whole lot of more sense to go with comps.xml groups and not
> > the silly RPM groups, since comps.xml allows to carry a lot more
> > descriptive information than Root/Branch, and allows packages to be
> > members of more than one group (sunbird, for example, is all of the
> > following: publishing, internet, communications, productivity,
> > editors).
> Nobody said that comps.xml support should be dropped. Neither did 
> anyone say that comps.xml is inferior to RPM groups.
> The problem is, how to procceed when there is no comps.xml file or the
> packages in question are not mentioned in the xml.
> 
> The current solution is to drop them into __nogroup__. A better idea would 
> be to fallback onto RPM groups in order to have _some_ kind of grouping.
> 

Right now if no comps.xml is found then repoview uses the rpm group tag
to categorize the packages.

It's done that for a while.

-sv