Re: Empty <grouphierarchy> in comps.xml?

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

 



Jeremy,

Is the same true for the <package> element?  If I have

<package>
<name>ash</name>
<dependencylist></dependencylist>
<name>bash</name>
<dependencylist></dependencylist>
...etc..
</package>

Will anaconda work for an automated install?  Or do I really need to
integrate the getfullcomps.py script into my tools?

getfullcomps.py seems to require RH 9 (rpm 4.2, python 2.2, rpm-python,
etc).  So far the rest of the kickstart tools do not require a specific
level of RH.

/Brian/

On Thu, 2003-07-03 at 16:09, Jeremy Katz wrote:
> On Thu, 2003-07-03 at 10:21, Brian Long wrote:
> > For automated kickstart, does the <grouphierarchy> element need to
> > contain valid subelements or can it be an empty element?  Will anaconda
> > barf if I just have <grouphierachy></grouphierarchy> in comps.xml?
> 
> It's only used during interactive installs to give the ordering in the
> UI.  If it's empty, then everything will just be put under the
> Miscellaneous header during an interactive install.
> 
> Cheers,
> 
> Jeremy
-- 
       Brian Long                      |         |           |
       Americas IT Hosting Sys Admin   |       .|||.       .|||.
       Cisco Linux Developer           |   ..:|||||||:...:|||||||:..
       Phone: (919) 392-7363           |   C i s c o   S y s t e m s




[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux