New Comps Groups

[Paul Howarth]

On Tue, 2006-11-28 at 14:52 -0500, Jesse Keating wrote:
> On Tuesday 28 November 2006 14:31, Nicolas Mailhot wrote:
> > The point is, people can classify properly packages, and apps choose to
> > show more or less groups depending on the target audience.
> >
> > For example repoview will typically show all groups, anaconda the most
> > important ones, yum something in between
> 
> But your hiding the package so NO tool will see it.  What is the point there?

The point is to be able to distinguish in a machine-parsable way the
difference between a package whose owner thinks that its purpose is as a
dependency of other packages and hence doesn't need to be visible to
users at package selection time (this sort of package would be in a
hidden group in the master comps file) and a package whose owner hasn't
thought about classification or has forgotten to enter the package in
the comps file for any other reason (such a package wouldn't be in the
master comps file at all). This allows easy checking for the latter case
by scripts (and subsequent nag mails or bug reports), which is not
currently possible.

Paul.