| 1 |
On Wed, Mar 18, 2020 at 4:16 PM Mart Raudsepp <leio@g.o> wrote: |
| 2 |
> |
| 3 |
> > @@ -1,6 +1,6 @@ |
| 4 |
> > -# Copyright 1999-2014 Gentoo Foundation |
| 5 |
> > +# Copyright 1999-2020 Gentoo Foundation |
| 6 |
> > # Distributed under the terms of the GNU General Public License v2 |
| 7 |
> > |
| 8 |
> > -USE="systemd udev" |
| 9 |
> > +USE="systemd udev user-session" |
| 10 |
> > |
| 11 |
> > BOOTSTRAP_USE="${BOOTSTRAP_USE} systemd udev" |
| 12 |
> |
| 13 |
> Seems good to me in principle, but I'm not sure it is something we |
| 14 |
> should do until we haven't promoted this into a global USE flag. |
| 15 |
|
| 16 |
An alternative would be to add entries in package.use. |
| 17 |
|
| 18 |
> With the disclaimer of not knowing anything about dbus[user-session] on |
| 19 |
> a non-systemd system - maybe it's just time to make user-session |
| 20 |
> unconditionally enabled on dbus (and then bluez) instead? |
| 21 |
> All it seems to do (on a very quick look) is install some extra systemd |
| 22 |
> files - can't they just be always installed (by always passing -- |
| 23 |
> enable-user-session) and call it a day? |
| 24 |
|
| 25 |
It looks like user-session has no effect if systemd is not in use. |
| 26 |
|
| 27 |
On systems running systemd, having the units installed automatically |
| 28 |
enables the systemd user bus, and the only way to disable it is to |
| 29 |
mask the units. Having the user bus enabled generally prevents display |
| 30 |
managers and startx from starting individual session buses, since they |
| 31 |
will use the user bus instead. That's probably fine, but I wanted to |
| 32 |
note it. |
Archives