summaryrefslogtreecommitdiff
path: root/dev-db/postgresql/postgresql-10.6.ebuild
diff options
context:
space:
mode:
authorMart Raudsepp <leio@gentoo.org>2019-03-20 11:36:42 +0200
committerMart Raudsepp <leio@gentoo.org>2019-03-20 11:50:44 +0200
commitbea47cee314829edbb41453d1e89fa1d1d3f9993 (patch)
tree9f0c0cff6e420edd57abc207b44f1f7061323b61 /dev-db/postgresql/postgresql-10.6.ebuild
parent672b3243cd44d1bbae47f46585232346344bf935 (diff)
downloadgentoo-bea47cee314829edbb41453d1e89fa1d1d3f9993.tar.gz
gentoo-bea47cee314829edbb41453d1e89fa1d1d3f9993.tar.bz2
gentoo-bea47cee314829edbb41453d1e89fa1d1d3f9993.zip
profiles/desktop/gnome: globally enable elogind, disable consolekit
GNOME really desires a logind provider. Now that the core gnome desktop supports elogind, we can default enable it in GNOME profile with a clean gnome-base/gnome install path without systemd. For this we also need to disable consolekit from desktop profile (until it's still enabled there), as some packages block between USE=consolekit and USE=elogind. profiles/desktop/gnome/systemd relies on the systemd profile now use.masking USE=elogind globally (a change I made some days ago), and enabling USE=systemd in its place, so should be no regressions there. Because stable doesn't have a usable non-systemd GNOME setup anyways, desktop/gnome profile wasn't out of the box usable, thus we don't need to concern ourselves for stable users here and get the profile working for ~arch users -- before this everyone using gnome should have been using desktop/gnome/systemd instead anyway. Bug: https://bugs.gentoo.org/599470 Signed-off-by: Mart Raudsepp <leio@gentoo.org>
Diffstat (limited to 'dev-db/postgresql/postgresql-10.6.ebuild')
0 files changed, 0 insertions, 0 deletions