One of the module has -native in its name which causes it to be provided
by both pipewire and pipewire-native and we need to set preferred
provider just for that. The fine tailored packages is not needed for
native case anyway so disable it
Fixes
NOTE: Multiple providers are available for runtime pipewire-modules-protocol-native (pipewire, pipewire-native)
Consider defining a PREFERRED_RPROVIDER entry to match pipewire-modules-protocol-native
Signed-off-by: Khem Raj <raj.khem@...>
---
meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.64.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.64.bb b/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.64.bb
index cc80989646..f10b472626 100644
--- a/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.64.bb
+++ b/meta-multimedia/recipes-multimedia/pipewire/pipewire_0.3.64.bb
@@ -246,6 +246,7 @@ PACKAGES =+ "\
"
PACKAGES_DYNAMIC = "^${PN}-spa-plugins.* ^${PN}-modules.*"
+PACKAGES_DYNAMIC:class-native = ""
SYSTEMD_SERVICE:${PN} = "${@bb.utils.contains('PACKAGECONFIG', 'systemd-system-service', 'pipewire.service', '', d)}"
CONFFILES:${PN} += "${datadir}/pipewire/pipewire.conf"
--
2.39.1
