wireplumber: dont start systemd system service by default

If wireplumber gets started with user services and socket activation,
what I guess is the regular way, the system service fails to come up at boot

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This commit is contained in:
Markus Volk 2022-12-29 19:56:46 +01:00 committed by Khem Raj
parent c9375defad
commit 7fc8426c45

View File

@ -124,7 +124,6 @@ PACKAGES =+ "\
PACKAGES_DYNAMIC = "^${PN}-modules.*"
SYSTEMD_SERVICE:${PN} = "wireplumber.service"
CONFFILES:${PN} += " \
${datadir}/wireplumber/wireplumber.conf \
${datadir}/wireplumber/*.lua.d/* \
@ -134,7 +133,7 @@ CONFFILES:${PN} += " \
# itself to become a daemon, in practice, the PipeWire daemon is used.
RRECOMMENDS:${PN} += "pipewire ${PN}-scripts ${PN}-modules-meta"
FILES:${PN} += "${systemd_user_unitdir}"
FILES:${PN} += "${systemd_user_unitdir} ${systemd_system_unitdir}"
FILES:libwireplumber = " \
${libdir}/libwireplumber-*.so.* \