On 8 February 2015 at 21:16, Christopher Larson <clar...@kergoth.com> wrote:
> DISTRO_FEATURES_append = " bluez5" >> PREFERRED_PROVIDER_bluez-hcidump = "bluez5" >> PNBLACKLIST[bluez-hcidump] = "superseded by bluez5" >> PNBLACKLIST[gst-plugin-bluetooth] = "dropped from bluez5" >> PNBLACKLIST[bluez4] = "superseded by bluez5" >> > > For what it's worth, I like the look of this series (and have since they > were first posted). Hopefully it gets merged. My concern with this series is using DISTRO_FEATURES to control what version of BlueZ is used in the image. What makes BlueZ so special that it deserves a DISTRO_FEATURE as opposed to a PREFERRED_PROVIDER_virtual/bluez or a variable such as BLUEZ_VERSION defined in bluetooth.bbclass? Oh, and gst-plugins-bad has support for BlueZ5 but this series doesn't enable it. Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
