Ühel kenal päeval, K, 18.03.2020 kell 16:43, kirjutas Mike Gilbert: > Seems good to me in principle, but I'm not sure it is something we > > should do until we haven't promoted this into a global USE flag. > > An alternative would be to add entries in package.use.
Yeah, that'd be what it is now, just done in systemd profile, not most of the separate systemd profiles. > > With the disclaimer of not knowing anything about dbus[user- > > session] on > > a non-systemd system - maybe it's just time to make user-session > > unconditionally enabled on dbus (and then bluez) instead? > > All it seems to do (on a very quick look) is install some extra > > systemd > > files - can't they just be always installed (by always passing -- > > enable-user-session) and call it a day? > > It looks like user-session has no effect if systemd is not in use. > > On systems running systemd, having the units installed automatically > enables the systemd user bus, and the only way to disable it is to > mask the units. Having the user bus enabled generally prevents > display > managers and startx from starting individual session buses, since > they > will use the user bus instead. That's probably fine, but I wanted to > note it. So how about we try to just always enable this instead in dbus and bluez? Anyone got any objections, provided the below can be handled? I peeked at bluez, and there USE=user-session exists to apply a patch to unbreak things when user-session is disabled. Unfortunately it seems to be needed there for non-systemd systems as well. I think we should be able to figure things out to work in all situations there, or make it be applied for USE=-systemd only (that's already the case there, just it is not applied for USE="systemd -user-session" right now). Mart
signature.asc
Description: This is a digitally signed message part
