- Rebuild the config files:
cp -a /etc/layman/layman.cfg /etc/layman/layman.cfg.bak
layman-updater --rebuild
- Delete the old Layman make.conf file (if it exists):
rm /var/lib/layman/make.conf
-
Remove the reference to the old Layman make.conf file (if it exists) with
nano -w /etc/portage/make.conf
:source /var/lib/layman/make.conf
This mode is no longer unofficially supported by
Gentoo Linux
since it now forces you to pick betweenelogind
andsystemd
.
This is GNOME without systemd and without basic functionality. This route is best suited if you:
- exclusively use startx
- don't need basic functionality
- want the GNOME ecosystem present while using another Desktop Environment¹
The primary benefit is that it does not require the project overlays (which contains ~200 ebuilds per GNOME release version) but instead requires you to create and occasionally maintain a local overlay (which will contain one or two ebuilds depending on circumstances). This allows you to follow whichever GNOME release is in the main portage tree without relying on a third party.
- Globally mask the systemd USE flag with
nano -w /etc/portage/profile/use.mask
:
systemd
-
Mask GDM >3.17.2 with
nano -w /etc/portage/package.mask/gdm
(or use a patched GDM)¹:Note: Since only the two most recent GNOME releases are kept in the main portage tree you'll have to fork an appropriate version of GDM. To expedite matters, simply choose from the relevant project overlays (since they all work): 3.14, 3.16, 3.18, 3.20, 3.22, 3.24, 3.26, 3.28, 3.30, 3.32, 3.34 or 3.36.
>gnome-base/gdm-3.17.2
-
Furthermore, if you intend to call GNOME Session as root (or use a patched GDM), mask ConsoleKit2 with
nano -w /etc/portage/package.mask/consolekit
:Note: For now it is sufficient to simply mask ConsoleKit2 but if in the future ConsoleKit is dropped from the main tree and its functionality is still needed, you'll have fork it too.
>sys-auth/consolekit-0.4.6
¹ It is sufficient to fake the presence of GDM instead if you don't intend to use it at all. ↩
As noted elsewhere¹, "this project's secondary purpose is to allow switching between GNOME release versions".
This means that for those seeking a specific GNOME release version, a lot of time can be saved by just using the project overlays. For OpenRC, no extra work is needed. For systemd, some profile changes need to be reversed:
- Disable the
Critical
² USE flags withnano -w /etc/portage/make.conf
:
# Critical
USE="${USE} -ck -elogind"
Disable the Aesthetic
² and Performant
² USE flags (and enable the Functional
USE flags) with nano -w /etc/portage/package.use/gnome
:
# Aesthetic and Performant
app-arch/file-roller -nautilus
gnome-base/gnome-control-center vanila-datetime
gnome-base/gnome-control-center vanila-hostname
gnome-base/gnome-shell -deprecated-background
gnome-base/gnome-shell vanilla-motd
gnome-base/gnome-shell vanilla-screen
gnome-base/nautilus vanilla-icon
gnome-base/nautilus vanilla-icon-grid
gnome-base/nautilus vanilla-menu
gnome-base/nautilus vanilla-menu-compress
gnome-base/nautilus vanilla-rename
gnome-base/nautilus vanilla-search
x11-terms/gnome-terminal -deprecated-transparency
x11-terms/gnome-terminal vanilla-hotkeys
x11-themes/gnome-backgrounds vanilla-live
x11-wm/mutter -deprecated-background
# Functional
gnome-base/gnome-session user-session
net-wireless/bluez user-session
sys-apps/dbus user-session
- Globally reverse the
systemd
USE flag mask withnano -w /etc/portage/profile/use.mask
:
-systemd
- Enable the systemd USE flag with
nano -w /etc/portage/make.conf
:
USE="${USE} systemd"
¹ For details, see: Long-term Solutions.
² For details, see: Classification.