pipewire: Avoid having pipewire-native depend on pipewirewalnascar-nextwalnascar

Make pipewire-pulse only depend on pipewire-modules-protocol-pulse for
target. Otherwise the magic behind BBCLASSEXTEND and PACKAGES_DYNAMIC
results in pipewire-native ending up depending on pipewire (for target).

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>

1 files changed, 3 insertions, 1 deletions

diff --git a/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.4.1.bb b/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.4.1.bb
index 122f8fc4ec..039087e3cf 100644
--- a/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.4.1.bb
+++ b/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.4.1.bb
@@ -334,7 +334,9 @@ FILES:${PN}-pulse = " \
     ${systemd_user_unitdir}/pipewire-pulse.* \
     ${bindir}/pipewire-pulse \
 "
-RDEPENDS:${PN}-pulse += " \
+# This uses :append:class-target rather than += to avoid a dependency from
+# pipewire-native to pipewire.
+RDEPENDS:${PN}-pulse:append:class-target = " \
     ${PN}-modules-protocol-pulse \
 "