On Wed, Mar 26, 2014 at 09:27:54AM -0500, Lauren Post wrote: > This group of patches support the change of hardcoded bluez4 to > virtual/bluez so that the upgrade to bluez5 is easier. > > This group of patches must be applied together. Bluez4 is still > default provider but it will be easier to override and provide bluez5 > support in future. >
> virtual/* still doesn't work correctly in runtime variables, use > VIRTUAL-RUNTIME_bluez variable. > Last time I've asked for bluez4->bluez5 upgrade path fix on target I was told > that it's not supported and > uez5 isn't drop-in replacement for > bluez4 (yet), did that change already? We are using bluez5.8 and have bbappends for all these components I patched. I just thought it would be easier to upstream rather than maintain all these bbappends. I missed the bluez5 change to virtual/bluez so will submit that once I rebuild with bluez5 as preferred provider on master. Lauren -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
