Browse Source

pipewire: Avoid having pipewire-native depend on pipewire

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: Khem Raj <raj.khem@gmail.com>
Peter Kjellerstedt 1 month ago
parent
commit
9f17bf73d7
1 changed files with 3 additions and 1 deletions
  1. 3 1
      meta-multimedia/recipes-multimedia/pipewire/pipewire_1.4.1.bb

+ 3 - 1
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 \
 "