[PATCH v2 0/1] YB5030: Multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) warning

[PATCH v2 0/1] YB5030: Multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) warning

[Cristian Iorga]

Patch V2:
Better commit message;
Opened a bug on the rather puzzling PREFERRED_PROVIDER fix,
that is refferenced in the commit message.

The following changes since commit 199b1a8c7d7109d9b59d67bf4dcfeb03be07587a:

  mkfontscale: This no longer needs a full libx11, xproto suffices (2013-08-22 18:30:06 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ciorga/bluez5_fixes
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ciorga/bluez5_fixes

Cristian Iorga (1):
  default-providers: Set the preferred provider for bluez

 meta/conf/distro/include/default-providers.inc | 1 +
 1 file changed, 1 insertion(+)

-- 
1.8.1.2

[PATCH v2 1/1] default-providers: Set the preferred provider for bluez

[Cristian Iorga]

There is a need for a default provider for bluez
now that bluez5 recipe is also present.

After the introduction of bluez5 recipe,
the following warnings are displayed:

"NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5)
 NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez"

Upon debug, bitbake shows:
DEBUG: checking PREFERRED_PROVIDER_bluez4 (value None) against ['bluez4', 'bluez5']
DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101 (value None) against ['bluez4', 'bluez5']
DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101-r5 (value None) against ['bluez4', 'bluez5']
DEBUG: checking PREFERRED_PROVIDER_bluez5 (value None) against ['bluez4', 'bluez5']
DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7 (value None) against ['bluez4', 'bluez5']
DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7-r0 (value None) against ['bluez4', 'bluez5']

Bitbake is faced with "what should provide libasound-module-bluez"
which is a runtime name. It needs to try and find a PREFERRED_PROVIDER
entry which matches this but those use *build time* naming.
So it converts "libasound-module-bluez" into
the canonical ${PN} of bluez4 and bluez5 and then
tries to look those up.
What it actually should do is go one step further
of mapping bluez4/bluex5 into the virtual/bluez
But that does not happen;

Bug opened on this issue: YB5044
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5044

Fixes [YOCTO #5030].

Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
---
 meta/conf/distro/include/default-providers.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/distro/include/default-providers.inc b/meta/conf/distro/include/default-providers.inc
index 67cc5f5..9255fd6 100644
--- a/meta/conf/distro/include/default-providers.inc
+++ b/meta/conf/distro/include/default-providers.inc
@@ -39,3 +39,4 @@ PREFERRED_PROVIDER_console-tools ?= "kbd"
 PREFERRED_PROVIDER_gzip-native ?= "pigz-native"
 PREFERRED_PROVIDER_make ?= "make"
 PREFERRED_PROVIDER_udev ?= "${@base_contains('DISTRO_FEATURES','systemd','systemd','udev',d)}"
+PREFERRED_PROVIDER_bluez4 ?= "bluez4"
-- 
1.8.1.2