<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 02/10/2015 09:43 AM, Burton, Ross
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAJTo0LaNQLGjMWDUQr0SMFDDRe3KTH_MxoUbHMJ9ex9W854jKg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On 8 February 2015 at 21:16,
            Christopher Larson <span dir="ltr">&lt;<a
                moz-do-not-send="true" href="mailto:clarson@kergoth.com"
                target="_blank">clarson@kergoth.com</a>&gt;</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>
    </blockquote>
    <br>
    Tried that first pass; I'll defer to RP and the list archives for
    the rationale.<br>
    <br>
    <blockquote
cite="mid:CAJTo0LaNQLGjMWDUQr0SMFDDRe3KTH_MxoUbHMJ9ex9W854jKg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <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>
    </blockquote>
    <br>
    I saw no sign of such support when I started back in November, and
    though the gst-plugins-bad master branch does have it now it looks
    like the package would have to be updated from 0.10.23 to enable
    it.  IMO that's out of scope.  My intent with this series is to make
    it possible to use bluez5 at all, not to make sure that every
    package that might work with bluez5 has support enabled.  That's
    best left to people who have the hardware/use-cases that allow such
    a configuration to be validated.<br>
    <br>
    Peter<br>
  </body>
</html>