[OE-core] [PATCH v2] pulseaudio: add systemd to PACKAGECONFIG if enabled in DISTRO_FEATURES

[Christopher Larson]

On Mon, Jul 13, 2015 at 3:23 AM, Pau Espin Pedrol <pespin.shar at gmail.com>
wrote:

> I am not sure which is the behavior with those paths right now and how
> it should be.
>
> I just checked this:
>
> http://www.freedesktop.org/software/systemd/man/systemd.unit.html#Unit%20Load%20Path
>
> So, it seems according to documentation that system services should be
> installed under /usr/lib/systemd/system, but currently they are
> installed in /lib/systemd/system in my generated image. Is that a
> expected behaviour? Shouldn't we try to follow documentation? I see
> that sometimes /lib/systemd/system path is appended to the dirs in
> systemdsystemunitpath, but it's not stated in the documentation,
> that's a bit strange.
>

Depends on the distro. Ubuntu, for example, uses /lib/systemd.


> For user services, /usr/lib/systemd/user is already being used as
> stated in docs.
>
> Now, when multilib comes in, I get lost. If I understand correctly,
> with multilib enabled we have too /lib64 and /usr/lib64. Are then
> systemd service files suppoused to be installed in /usr/lib/systemd/
> or in /usr/lib64/systemd/ ? If I undersood correctly your comment you
> meant they should still be going into /usr/lib/systemd right?
>

Yes, we don’t want arch-independent files going into arch-specific dirs.

Now, talking about bitbake.conf. I see there's already a line with the
> following:
> export systemd_unitdir = "/lib/systemd"
>
> So, apart from your nonarch issue, I think it would also be a good
> idea to split systemd_unitdir into system and user, as done by
> provided pc in systemd (src/core/systemd.pc.in):
> 1- If still want system services to be in /lib and user services to be
> in /usr/lib:
> export nonarch_libdir = "${prefix}/lib"
>
> export systemd_system_unitdir = "${nonarch_base_libdir}/systemd/system"
> export systemd_user_unitdir = "${nonarch_libdir}/systemd/user"
> or
> export systemd_system_unitdir = "${nonarch_base_libdir}/systemd"
> export systemd_user_unitdir = "${nonarch_libdir}/systemd"
>
>
> 2- If you want both in /usr/lib:
> export nonarch_libdir = "${prefix}/lib"
>
> export systemd_system_unitdir = "${nonarch_libdir}/systemd/system"
> export systemd_user_unitdir = "${nonarch_libdir}/systemd/user"
> or
> export systemd_system_unitdir = "${nonarch_libdir}/systemd"
> export systemd_user_unitdir = "${nonarch_libdir}/systemd"
>

I don’t really see why one would want some of their service files in one
libdir and the rest in another. Is there a reason to not just obey
systemd_unitdir in pulseaudio?
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150713/0d456eb8/attachment-0002.html>