On 31 October 2013 12:14, Rongqing Li wrote:
> connman can detect whether Bluez 4.x or Bluez 5.x is running, so both
> versions are ok for it.
>
> I think all packages should have the capability to detect which bluez
> version is used.
Whereas the GNOME platform has (last time I looked) mandated
On 10/31/2013 12:51 PM, Mark Hatle wrote:
On 10/30/13, 7:59 PM, rongqing...@windriver.com wrote:
From: Roy Li
We have two version bluez, declare virtual/bluez to switch them easily,
and set the preferred provider for bluez as bluez4
Unfortunately, I'm not sure this will work. (I am not a
On 10/31/2013 04:12 PM, Martin Jansa wrote:
On Thu, Oct 31, 2013 at 08:59:51AM +0800, rongqing...@windriver.com wrote:
From: Roy Li
We have two version bluez, declare virtual/bluez to switch them easily,
and set the preferred provider for bluez as bluez4
virtual/bluez and PREFERRED_PROVIDE
On Thu, Oct 31, 2013 at 08:59:51AM +0800, rongqing...@windriver.com wrote:
> From: Roy Li
>
> We have two version bluez, declare virtual/bluez to switch them easily,
> and set the preferred provider for bluez as bluez4
virtual/bluez and PREFERRED_PROVIDERS doesn't work for runtime
dependencies,
On 10/30/13, 7:59 PM, rongqing...@windriver.com wrote:
From: Roy Li
We have two version bluez, declare virtual/bluez to switch them easily,
and set the preferred provider for bluez as bluez4
Unfortunately, I'm not sure this will work. (I am not a BlueZ expert!) I've
been told that BlueZ 4
From: Roy Li
We have two version bluez, declare virtual/bluez to switch them easily,
and set the preferred provider for bluez as bluez4
Signed-off-by: Roy Li
---
meta/conf/distro/include/default-providers.inc|4 +---
meta/recipes-connectivity/bluez/bluez4.inc
