5031 2013-08-20 17:36:25 +0000 BlueZ5 needs to be available to packages that wants to use it 2015-02-17 16:01:44 +0000 1 1 7 Build System, Metadata & Runtime OE-Core connectivity 1.5 All Multiple RESOLVED FIXED Medium normal 1.8 M3 1 cristian.iorga cristian.iorga meta.mr.watcher meta.watcher sgw --- --- Yes (doc changes required) oldest_to_newest 35781 0 cristian.iorga 2013-08-20 17:36:25 +0000 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. 35782 1 cristian.iorga 2013-08-20 17:37:43 +0000 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. 36372 2 mihai.prica 2013-09-06 12:46:34 +0000 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. 40674 3 cristian.iorga 2014-02-25 11:09:49 +0000 Pushed back due to task prioritization. 48862 4 cristian.iorga 2015-02-16 14:56:19 +0000 Investigation started. 48884 5 cristian.iorga 2015-02-17 16:01:44 +0000 Fixed with commit: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3f8c532e6d478afcae15580bfe3ec33f89319d50