Re: Guide to comps.xml and friends

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

 



On Wed, 2005-06-08 at 14:26, dan wrote:
> Brian Long wrote:
> > On Tue, 2005-06-07 at 23:47, Jeremy Katz wrote:
> > 
> >>On Tue, 2005-06-07 at 18:38 -0700, dan wrote:
> >>
> >>>However, I was wondering if anyone has found, or has in their posession, 
> >>>a comprehensive guide to comps.xml, detailing which packages have which 
> >>>dependencies, which groups are inherited, which groups are required, the 
> >>>true definition of each directive (<packagereq 
> >>>type="[default][mandatory][optional]>, for instance)... stuff like that. 
> >>
> >>The format is defined at http://rhlinux.redhat.com/anaconda/comps.html
> >>
> >>Jeremy
> > 
> > 
> > Jeremy, this page was never updated for RHEL 3 where you removed the
> > <package> sections since Anaconda auto-computes dependencies.
> > 
> > Also, the whole section on getfullcomps.py doesn't apply to supported
> > releases.
> > 
> > /Brian/
> > 
> 
> 
> Thanks for the heads-up Brian.  Does this mean that the list that Jeremy 
> had posted does not apply for RHEL3+ systems?

It means you no longer need to have the packages section or run
getfullcomps.py.  You just have groups and grouphierarchy.  Look at the
comps.xml that comes on the ISO and you'll see what I mean.

/Brian/


[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux