On Fri, 2014-10-24 at 13:02 +0100, Colin Guthrie wrote: > Tanu Kaskinen wrote on 24/10/14 12:08: > > On Fri, 2014-10-24 at 11:14 +0100, Colin Guthrie wrote: > >> Tanu Kaskinen wrote on 24/10/14 10:42: > >>> "Disable the manual override" doesn't sound like a good idea... Does > >>> this mean that "systemctl --user disable pulseaudio.socket" doesn't > >>> work? > >> > >> Yes, but it also has the advantage that every single user on the system > >> doesn't have to run "systemctl --user enable pulseaudio.socket" before > >> their sound will work. If distros ship this, they will definitely ship > >> this symlink or something similar to it, so I think doing this by > >> default makes sense for us too. > > > > I expect distros to enable the service only on first install, not on > > package updates. > > I expect distros to completely forget this step and then complain - > especially so because this is a user socket unit, not a system on and > the packaging guidelines for such things are still in their relative > infancy. > > But I'm not strongly against it, but I just don't like the fact that > this enabling, if done in packaging, would hence be in /etc tree and > thus also suffer from a "factory reset" unless corresponding tmpfiles > rules were also put in place to recreate the symlink.
Good point, enabling the service under /etc is not optimal either. In the other thread you were convinced that we shouldn't install the default.target.wants link, but I'm starting to be convinced that we should :) I'm still annoyed by the fact that users can't use "systemctl --user disable pulseaudio", but there doesn't seem to be any better way for upstreams/distros to enable services by default (this seems very odd to me, since all other configuration in systemd can be cleanly overridden at multiple levels). -- Tanu _______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
