Hi,
Is there proper documentation on what package groups (names, ids) are allowed in kickstart files these days?
I've read http://fedoraproject.org/wiki/Features/ReworkPackageGroups but that doesn't explain details on how it's implemented..
I used to look at comps.xml and/or I ran "yum grouplist -v" to find what groups I wanted, but the few groups I tried don't seem to be accepted (anymore).
Thanks for a any help,
-- -- Jos Vos jos@xos.nl -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204
On Sun, 2013-03-24 at 14:40 +0100, Jos Vos wrote:
Hi,
Is there proper documentation on what package groups (names, ids) are allowed in kickstart files these days?
I've read http://fedoraproject.org/wiki/Features/ReworkPackageGroups but that doesn't explain details on how it's implemented..
I used to look at comps.xml and/or I ran "yum grouplist -v" to find what groups I wanted, but the few groups I tried don't seem to be accepted (anymore).
It's still what's listed in comps. What are you trying that doesn't work?
On Sun, 24 Mar 2013 09:32:35 -0700 Adam Williamson awilliam@redhat.com wrote:
On Sun, 2013-03-24 at 14:40 +0100, Jos Vos wrote:
Hi,
Is there proper documentation on what package groups (names, ids) are allowed in kickstart files these days?
I've read http://fedoraproject.org/wiki/Features/ReworkPackageGroups but that doesn't explain details on how it's implemented..
I used to look at comps.xml and/or I ran "yum grouplist -v" to find what groups I wanted, but the few groups I tried don't seem to be accepted (anymore).
It's still what's listed in comps. What are you trying that doesn't work?
yum grouplist hidden -v
Should get them all (and list short names too).
kevin
On Sun, Mar 24, 2013 at 10:37:02AM -0600, Kevin Fenzi wrote:
yum grouplist hidden -v
Should get them all (and list short names too).
Thanks, this saves me manually parsing comps.xml.
On Sun, Mar 24, 2013 at 09:32:35AM -0700, Adam Williamson wrote:
It's still what's listed in comps. What are you trying that doesn't work?
True. I was confused by (the combination of) the "category" items in comps.xml (they can't be used it seems, wouldn't it be a good idea to allow them too?), the now obsoleted examples in the F18 installation guide http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/s1-kic... and what was listed in http://fedoraproject.org/wiki/Features/ReworkPackageGroups .
Jos Vos (jos@xos.nl) said:
On Sun, Mar 24, 2013 at 09:32:35AM -0700, Adam Williamson wrote:
It's still what's listed in comps. What are you trying that doesn't work?
True. I was confused by (the combination of) the "category" items in comps.xml (they can't be used it seems, wouldn't it be a good idea to allow them too?), the now obsoleted examples in the F18 installation guide http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/s1-kic... and what was listed in http://fedoraproject.org/wiki/Features/ReworkPackageGroups .
categories remains for use by the assorted post-install tools as items that guide the UI; they are not used in anaconda. Anaconda uses the environment groups.
Bill
On Mon, Mar 25, 2013 at 03:05:38PM -0400, Bill Nottingham wrote:
categories remains for use by the assorted post-install tools as items that guide the UI; they are not used in anaconda. Anaconda uses the environment groups.
But it does not seem to be possible to specify an environment as group in kickstart's %packages, right?
Jos Vos (jos@xos.nl) said:
On Mon, Mar 25, 2013 at 03:05:38PM -0400, Bill Nottingham wrote:
categories remains for use by the assorted post-install tools as items that guide the UI; they are not used in anaconda. Anaconda uses the environment groups.
But it does not seem to be possible to specify an environment as group in kickstart's %packages, right?
Correct, as of now.
You can do yum install ^<environment-name>, or yum groupinstall <environment-name>, and have it work on the yum commandline. It's not plugged into kickstart, though.
Bill