<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 8 February 2015 at 21:16, Christopher Larson <span dir="ltr"><<a href="mailto:clarson@kergoth.com" target="_blank">clarson@kergoth.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="overflow:hidden"> DISTRO_FEATURES_append = " bluez5"<br>
PREFERRED_PROVIDER_bluez-hcidump = "bluez5"<br>
PNBLACKLIST[bluez-hcidump] = "superseded by bluez5"<br>
PNBLACKLIST[gst-plugin-bluetooth] = "dropped from bluez5"<br>
PNBLACKLIST[bluez4] = "superseded by bluez5"</div></blockquote></div><br></span>For what it's worth, I like the look of this series (and have since they were first posted). Hopefully it gets merged.</blockquote></div><br>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?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Oh, and gst-plugins-bad has support for BlueZ5 but this series doesn't enable it.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>