Bug 5031

Summary: BlueZ5 needs to be available to packages that wants to use it
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Cristian Iorga <cristian.iorga>
Component: connectivityAssignee: Cristian Iorga <cristian.iorga>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher, sgw
Version: 1.5   
Target Milestone: 1.8 M3   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Cristian Iorga 2013-08-20 17:36:25 UTC 
It's possible for new version of ofono or connman to want to use bluez5, via the PACKAGECONFIG settings, we need to allow that to happen without having to embed bluez4 vs bluez5 in the recipe.
Comment 1 Cristian Iorga 2013-08-20 17:37:43 UTC 
This can be done with a virtual/bluez style of declaration.
Examples of this can be seen for virtual/libc and in the meta/conf/distro/include/default-providers.inc file.
Comment 2 Mihai Prica 2013-09-06 12:46:34 UTC 
From what I see, this can not be done using PACKAGECONFIG without breaking some things. The only clean way is the solution proposed by Cristian with a virtual/bluez style that should be used by all packages, but the problem is that not all packages have support for bluez5.

This should be postponed until there is more support for bluez5.
Comment 3 Cristian Iorga 2014-02-25 11:09:49 UTC 
Pushed back due to task prioritization.
Comment 4 Cristian Iorga 2015-02-16 14:56:19 UTC 
Investigation started.