[pulseaudio-discuss] [PATCH 6/8] launch: Add systemd units for launching pulseaudio user instances
Colin Guthrie
gmane at colin.guthr.ie
Mon Nov 10 08:58:29 PST 2014
Glenn Golden wrote on 10/11/14 16:39:
> Tanu Kaskinen <tanu.kaskinen at linux.intel.com> [2014-11-10 18:29:16 +0200]:
>>
>> Are you sure installing to /usr/local/lib/systemd/user doesn't work? To
>> me path-lookup.c looks like it includes /usr/local/lib/systemd/user in
>> the unit search paths.
>>
>
> Fwiw, just as an empirical datapoint here: I run Arch linux, which is pretty
> much a bleeding edge distro, and I keep it up to date every 5-10 days.
> On my system, numerous non-core packages have been installed, and so far,
> among those which provide user systemd service units, none have installed the
> service unit files in /usr/local/lib/systemd.
>
> (In fact, there isn't even a /usr/local/lib/systemd directory on my system.)
>
> Not implying that this "proves" anything at all about installation conventions,
> just tossing it out as an empircal observation in case it may be of use.
I wouldn't expect any distro to *ship* stuff in /usr/local. It's the
path used for stuff that's outside of distro territory - i.e. what users
do on their system outside of "packaged" stuff.
So the fact that /usr/local/... is empty or non-existent is pretty much
the expected behaviour :)
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited http://www.tribalogic.net/
Open Source:
Mageia Contributor http://www.mageia.org/
PulseAudio Hacker http://www.pulseaudio.org/
Trac Hacker http://trac.edgewall.org/
More information about the pulseaudio-discuss
mailing list