As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
Based on what's in the kickstart file for the Desktop spin, here's what I have for the Desktop:
GNOME contains: desktop-backgrounds-basic control-center dconf gnome-panel gnome-session gnome-shell gnome-themes-standard metacity notification-daemon abrt-desktop aisleriot at-spi2-atk at-spi2-core avahi baobab brasero-nautilus caribou cheese deja-dup eog evince evince-nautilus file-roller file-roller-nautilus fprintd-pam gcalctool gdm gedit glib-networking gnome-backgrounds gnome-bluetooth gnome-color-manager gnome-contacts gnome-dictionary gnome-disk-utility gnome-disk-utility-nautilus gnome-documents gnome-font-viewer gnome-icon-theme gnome-icon-theme-extras gnome-icon-theme-symbolic gnome-packagekit gnome-screensaver gnome-screenshot gnome-system-log gnome-system-monitor gnome-terminal gnome-user-docs gucharmap gvfs-fuse gvfs-gphoto2 gvfs-smb libcanberra-gtk2 libcanberra-gtk3 libproxy-mozjs librsvg2 libsane-hpaio mousetweaks nautilus nautilus-sendto NetworkManager-gnome NetworkManager-openconnect NetworkManager-openvpn NetworkManager-pptp NetworkManager-vpnc orca PackageKit-command-not-found PackageKit-gtk-module PackageKit-gtk3-module policycoreutils-restorecond polkit-gnome seahorse sushi xdg-user-dirs-gtk yelp firefox icedtea-web
and has the following 'options' available: gnome-apps: empathy evolution evolution-help evolution-NetworkManager gnome-boxes gnome-games shotwell simple-scan sane-backends-drivers-scanners vinagre vino gnome-media: brasero rhythmbox sound-juicer totem totem-mozplugin totem-nautilus libreoffice: libreoffice-calc libreoffice-draw libreoffice-graphicfilter libreoffice-impress libreoffice-math libreoffice-writer libreoffice-xsltfilter
I welcome any and all sanity-checking of this, and ideas for additions/removals. You can open the current F18/F19 comps files and see the data that makes this up - the 'gnome-desktop' environment defines what groups go into GNOME, and which are shown as options, and the groups referenced there define what packages make them up.
Thanks, Bill
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
I welcome any and all sanity-checking of this, and ideas for additions/removals. You can open the current F18/F19 comps files and see the data that makes this up - the 'gnome-desktop' environment defines what groups go into GNOME, and which are shown as options, and the groups referenced there define what packages make them up.
From a quick look, it seems that gnome-settings-daemon is missing
(although it will probably get pulled in by deps), and epiphany should probably be listed under options.
Matthias Clasen (mclasen@redhat.com) said:
I welcome any and all sanity-checking of this, and ideas for additions/removals. You can open the current F18/F19 comps files and see the data that makes this up - the 'gnome-desktop' environment defines what groups go into GNOME, and which are shown as options, and the groups referenced there define what packages make them up.
From a quick look, it seems that gnome-settings-daemon is missing (although it will probably get pulled in by deps), and epiphany should probably be listed under options.
OK, added. Thanks!
Bill
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
From what I can see a lot of this is shuffling around where metadata
lives and how it's presented, which sounds fine, but is kind of uninteresting.
However, the "yum is changed so that persistent groups are enabled by default" seems to me to have more significant ramifications. Does it mean that we no longer need to add artificial dependencies just to ensure that new packages are pulled in on upgrades, for example?
Or do we still need to do that to handle the case where the user is upgrading a pre-persistent-groups system?
Colin Walters (walters@verbum.org) said:
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
From what I can see a lot of this is shuffling around where metadata lives and how it's presented, which sounds fine, but is kind of uninteresting.
Yeah, it's more interesting in what it allows us to use (have spins be more consistent across install methods, and less tied to each other), than it is directly for the user.
However, the "yum is changed so that persistent groups are enabled by default" seems to me to have more significant ramifications. Does it mean that we no longer need to add artificial dependencies just to ensure that new packages are pulled in on upgrades, for example?
That's the idea, but...
Or do we still need to do that to handle the case where the user is upgrading a pre-persistent-groups system?
... there's going to be a lot of these users.
Bill
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
Based on what's in the kickstart file for the Desktop spin, here's what I have for the Desktop:
NetworkManager-gnome is dead, having been replaced by both network-manager-applet and nm-connection-editor, among others. At this point, the Shell is functional enough that we don't need network-manager-applet anymore for GNOME desktops. But we still need nm-connection-editor.
Dan
GNOME contains: desktop-backgrounds-basic control-center dconf gnome-panel gnome-session gnome-shell gnome-themes-standard metacity notification-daemon abrt-desktop aisleriot at-spi2-atk at-spi2-core avahi baobab brasero-nautilus caribou cheese deja-dup eog evince evince-nautilus file-roller file-roller-nautilus fprintd-pam gcalctool gdm gedit glib-networking gnome-backgrounds gnome-bluetooth gnome-color-manager gnome-contacts gnome-dictionary gnome-disk-utility gnome-disk-utility-nautilus gnome-documents gnome-font-viewer gnome-icon-theme gnome-icon-theme-extras gnome-icon-theme-symbolic gnome-packagekit gnome-screensaver gnome-screenshot gnome-system-log gnome-system-monitor gnome-terminal gnome-user-docs gucharmap gvfs-fuse gvfs-gphoto2 gvfs-smb libcanberra-gtk2 libcanberra-gtk3 libproxy-mozjs librsvg2 libsane-hpaio mousetweaks nautilus nautilus-sendto NetworkManager-gnome NetworkManager-openconnect NetworkManager-openvpn NetworkManager-pptp NetworkManager-vpnc orca PackageKit-command-not-found PackageKit-gtk-module PackageKit-gtk3-module policycoreutils-restorecond polkit-gnome seahorse sushi xdg-user-dirs-gtk yelp firefox icedtea-web
and has the following 'options' available: gnome-apps: empathy evolution evolution-help evolution-NetworkManager gnome-boxes gnome-games shotwell simple-scan sane-backends-drivers-scanners vinagre vino gnome-media: brasero rhythmbox sound-juicer totem totem-mozplugin totem-nautilus libreoffice: libreoffice-calc libreoffice-draw libreoffice-graphicfilter libreoffice-impress libreoffice-math libreoffice-writer libreoffice-xsltfilter
I welcome any and all sanity-checking of this, and ideas for additions/removals. You can open the current F18/F19 comps files and see the data that makes this up - the 'gnome-desktop' environment defines what groups go into GNOME, and which are shown as options, and the groups referenced there define what packages make them up.
Thanks, Bill
On Thu, 2012-08-23 at 11:03 -0500, Dan Williams wrote:
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
Based on what's in the kickstart file for the Desktop spin, here's what I have for the Desktop:
NetworkManager-gnome is dead, having been replaced by both network-manager-applet and nm-connection-editor, among others. At this point, the Shell is functional enough that we don't need network-manager-applet anymore for GNOME desktops. But we still need nm-connection-editor.
We'll need it until we can get rid of fallback :(
On 08/23/2012 06:04 PM, Bastien Nocera wrote:
On Thu, 2012-08-23 at 11:03 -0500, Dan Williams wrote:
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
Based on what's in the kickstart file for the Desktop spin, here's what I have for the Desktop:
NetworkManager-gnome is dead, having been replaced by both network-manager-applet and nm-connection-editor, among others. At this point, the Shell is functional enough that we don't need network-manager-applet anymore for GNOME desktops. But we still need nm-connection-editor.
We'll need it until we can get rid of fallback :(
Hey all,
we've just submitted the Fedora Audio spin for the first time. I'm thinking that perhaps all of the packages should be present in the comps file on install. What do you think?
bsjones
Bastien Nocera (bnocera@redhat.com) said:
On Thu, 2012-08-23 at 11:03 -0500, Dan Williams wrote:
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
Based on what's in the kickstart file for the Desktop spin, here's what I have for the Desktop:
NetworkManager-gnome is dead, having been replaced by both network-manager-applet and nm-connection-editor, among others. At this point, the Shell is functional enough that we don't need network-manager-applet anymore for GNOME desktops. But we still need nm-connection-editor.
We'll need it until we can get rid of fallback :(
OK, I will make the appropriate substitutions. As an aside:
*NetworkManager*{-glib,-openvpn,-vpnc,etc.} *network-manager*-applet *nm*-connection-editor
Not saying we need 100% consistency, but a little might be nice.
Bill
On Thu, 2012-08-23 at 13:36 -0400, Bill Nottingham wrote:
Bastien Nocera (bnocera@redhat.com) said:
On Thu, 2012-08-23 at 11:03 -0500, Dan Williams wrote:
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've been working on redoing some of the groups that make up installation choices in anaconda. The idea is to offer a simpler interface, where the user simply selects which environment they want to run in, plus options for that environment.
Based on what's in the kickstart file for the Desktop spin, here's what I have for the Desktop:
NetworkManager-gnome is dead, having been replaced by both network-manager-applet and nm-connection-editor, among others. At this point, the Shell is functional enough that we don't need network-manager-applet anymore for GNOME desktops. But we still need nm-connection-editor.
We'll need it until we can get rid of fallback :(
OK, I will make the appropriate substitutions. As an aside:
*NetworkManager*{-glib,-openvpn,-vpnc,etc.} *network-manager*-applet *nm*-connection-editor
Not saying we need 100% consistency, but a little might be nice.
Would be nice, and I tried to create "NetworkManager-applet" repos on gnome.org when we moved the git repos there a few years ago, but for whatever @%#%@# reason gnome.org has a policy of refusing StudlyCaps repo names. So I had to name the repo network-manager-applet. And since our package names follow our tarball names...
Dan
On 2012-08-23 9:04, Bastien Nocera wrote:
On Thu, 2012-08-23 at 11:03 -0500, Dan Williams wrote:
On Fri, 2012-08-17 at 15:18 -0400, Bill Nottingham wrote:
As part of
https://fedoraproject.org/wiki/Features/ReworkPackageGroups, I've
been working on redoing some of the groups that make up
installation choices
in anaconda. The idea is to offer a simpler interface, where the
user simply
selects which environment they want to run in, plus options for
that
environment.
Based on what's in the kickstart file for the Desktop spin, here's
what I
have for the Desktop:
NetworkManager-gnome is dead, having been replaced by both network-manager-applet and nm-connection-editor, among others. At this point, the Shell is functional enough that we don't need network-manager-applet anymore for GNOME desktops. But we still need nm-connection-editor.
We'll need it until we can get rid of fallback :(
As things stand you need it for longer than that. The 'Network' part of control-center actually runs nm-connection-editor to configure certain types of connections, like VPNs. See https://bugzilla.redhat.com/show_bug.cgi?id=849268 .
desktop@lists.fedoraproject.org
-
Adam Williamson -
Bastien Nocera -
Bill Nottingham -
Brendan Jones -
Colin Walters -
Dan Williams -
Matthias Clasen