On first install, that all users that pull it in as a dep of an extensions package will probably get: * Updating list of installed extensions /usr/share/eselect/modules/gnome-shell-extensions.eselect: line 78: pushd: //usr/share/gnome-shell/extensions: No such file or directory !!! Warning: Failed to open //usr/share/gnome-shell/extensions If actually installing it separately, not as an extension dependency (so no extensions will be present): localhost gnome # eselect gnome-shell-extensions list /usr/share/eselect/modules/gnome-shell-extensions.eselect: line 78: pushd: /usr/share/gnome-shell/extensions: No such file or directory Available extensions (* means enabled by default): (none found) !!! Warning: Failed to open /usr/share/gnome-shell/extensions Also the elog text seems that it could be very confusing to someone who doesn't infer what the disabled-extensions key would do
With gnome-shell-3.1.90, the eselect module is no longer needed, since gnome-shell finally got a sane system for extension management. Specifically, (1) all extensions are disabled by default, and (2) there is a nice dbus interface for enabling/disabling them. I'm wondering whether the best solution is to just wait 1 month until gnome-shell-3.2 is released :) Or maybe backport the disabled-by-default 3.1.90 behavior to gnome-shell-3.0, if we want to get all of gnome3 into portage faster.
After a discussion in #gentoo-desktop ~10 days ago, it was decided that the eselect module should be kept since it can still be useful in gnome-3.2 (e.g. for people who want to enable an extension for all users on a machine). I have added eselect-gnome-shell-extensions-20110911 to the overlay; it should fix the pushd warning problem, and works with both 3.0 and 3.2.
