Peter Robinson (pbrobinson@gmail.com) said:
Honestly, I could see exploding it into a variety of smaller, more focused groups. Perhaps I'll whip up a proposal based on some comps files I have lying around here.
I've spent a little time looking at the hardware side of things and done a basic patch for some of the hardware stuff based on the current rawhide comps file. I've broken it down into network/server/misc for the time being and pushed the print stuff over to its group. More can be done as it was a quick look through. The old hardware-support currently includes all the other groups so there's no real change for current builds overall.
Splitting it by functionality makes a bit more sense; for example, you'd want a 'smart card support', not just merging it in with other hardware stuff.
(Sorry I've let this lie... been way too busy.)
Also, I'm not sure the grouplist construct works as you're trying to use it.
I also noticed that alot of the filesystems group lists are replicated into base. I think base should have the core ext related tools to boot a default Fedora and the other stuff like ntfs should just remain in the filesystems group.
Actually, anaconda will pull in the ones you use for formatting if needed.
Bill
On Wed, Apr 21, 2010 at 3:48 PM, Bill Nottingham notting@redhat.com wrote:
Peter Robinson (pbrobinson@gmail.com) said:
Honestly, I could see exploding it into a variety of smaller, more focused groups. Perhaps I'll whip up a proposal based on some comps files I have lying around here.
I've spent a little time looking at the hardware side of things and done a basic patch for some of the hardware stuff based on the current rawhide comps file. I've broken it down into network/server/misc for the time being and pushed the print stuff over to its group. More can be done as it was a quick look through. The old hardware-support currently includes all the other groups so there's no real change for current builds overall.
Splitting it by functionality makes a bit more sense; for example, you'd want a 'smart card support', not just merging it in with other hardware stuff.
(Sorry I've let this lie... been way too busy.)
Also, I'm not sure the grouplist construct works as you're trying to use it.
OK, I just cut and paste it out of other places in the config file so I may have missed something. Suggestions?
I also noticed that alot of the filesystems group lists are replicated into base. I think base should have the core ext related tools to boot a default Fedora and the other stuff like ntfs should just remain in the filesystems group.
Actually, anaconda will pull in the ones you use for formatting if needed.
So the base shouldn't need any file systems then and it should all just be in the file systems group?
Peter
Peter Robinson (pbrobinson@gmail.com) said:
Splitting it by functionality makes a bit more sense; for example, you'd want a 'smart card support', not just merging it in with other hardware stuff.
(Sorry I've let this lie... been way too busy.)
Also, I'm not sure the grouplist construct works as you're trying to use it.
OK, I just cut and paste it out of other places in the config file so I may have missed something. Suggestions?
Not sure you can make it seamless without just copy&pasting the entire group (which is a bad idea). <grouplist> within <group> is ignored in comps.
Actually, anaconda will pull in the ones you use for formatting if needed.
So the base shouldn't need any file systems then and it should all just be in the file systems group?
Or they shouldn't need to necessarily be in a group at all, possibly. Depends on how you want to get them installed. (For example, dosfstools and perhaps the ntfs tools should be included in a desktop where you're expected to access those sorts of filesystems. reiserfs, not so much.)
Bill
On Wed, Apr 21, 2010 at 4:12 PM, Bill Nottingham notting@redhat.com wrote:
Peter Robinson (pbrobinson@gmail.com) said:
Splitting it by functionality makes a bit more sense; for example, you'd want a 'smart card support', not just merging it in with other hardware stuff.
(Sorry I've let this lie... been way too busy.)
Also, I'm not sure the grouplist construct works as you're trying to use it.
OK, I just cut and paste it out of other places in the config file so I may have missed something. Suggestions?
Not sure you can make it seamless without just copy&pasting the entire group (which is a bad idea). <grouplist> within <group> is ignored in comps.
Ah, I just copied the xfce-software-development as it was small and had what I wanted. What's the proper way to do this then? Looking further down the file the Desktops category looks like it would be what I want.
Actually, anaconda will pull in the ones you use for formatting if needed.
So the base shouldn't need any file systems then and it should all just be in the file systems group?
Or they shouldn't need to necessarily be in a group at all, possibly. Depends on how you want to get them installed. (For example, dosfstools and perhaps the ntfs tools should be included in a desktop where you're expected to access those sorts of filesystems. reiserfs, not so much.)
Again, I was just looking at what's in the comps file already.
Peter
Peter Robinson (pbrobinson@gmail.com) said:
Not sure you can make it seamless without just copy&pasting the entire group (which is a bad idea). <grouplist> within <group> is ignored in comps.
Ah, I just copied the xfce-software-development as it was small and had what I wanted. What's the proper way to do this then? Looking further down the file the Desktops category looks like it would be what I want.
Categories aren't a yum-able object; they're used by anaconda only.
Bill
On Wed, 21 Apr 2010, Bill Nottingham wrote:
Peter Robinson (pbrobinson@gmail.com) said:
Not sure you can make it seamless without just copy&pasting the entire group (which is a bad idea). <grouplist> within <group> is ignored in comps.
Ah, I just copied the xfce-software-development as it was small and had what I wanted. What's the proper way to do this then? Looking further down the file the Desktops category looks like it would be what I want.
Categories aren't a yum-able object; they're used by anaconda only.
Like I said before - categories can be used by any yum api-caller.
but they aren't available to anything using yum from the cli.
import yum my = yum.YumBase() my.setCacheDir() c = my.comps.categories[0] print c Desktop Environments print c.groups ['gnome-desktop', 'sugar-desktop', 'window-managers', 'kde-desktop', 'lxde-desktop', 'moblin-desktop', 'xfce-desktop']
-sv
desktop@lists.fedoraproject.org
-
Bill Nottingham -
Peter Robinson -
Seth Vidal