From: "Peter A. Bigot" <pab@pabigot.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/5] bluetooth.bbclass: set bluez5 as the default BT stack
Date: Mon, 06 Apr 2015 07:57:59 -0500 [thread overview]
Message-ID: <552282D7.6040108@pabigot.com> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB2F4944D2@irsmsx105.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
On 04/06/2015 02:31 AM, Iorga, Cristian wrote:
>
> I thought of 1.9 as the preparatory stage for complete removal of
> bluez4, so that in 2.0 it would be very easy to remove the support for
> bluez4. Continuing to have bluez5 added to DISTRO_FEATURES create the
> impression that BlueZ5 is still a second class citizen compared to
> BlueZ4, and it is not my intention to sustain this opinion via code.
>
> I hereby standup for my solution. At the moment, we are 1to1. “We
> think” – Who are the others persons, Ross?
>
> /Cristian
>
While I fully support moving to bluez5 and use it in all my images, I do
think it's a bit abrupt to make it the default in the first stable
release that provides a usable bluez5. On the other hand, Yocto's late
to the bluez5 party and it's going to be harder to support bluez4 now.
Six of one; sign me up as weak support for delaying the move to default
bluez5 until 1.10.
Just an opinion.
Peter
>
> *From:*Burton, Ross [mailto:ross.burton@intel.com]
> *Sent:* Monday, April 6, 2015 12:41 AM
> *To:* Iorga, Cristian
> *Cc:* OE-core
> *Subject:* Re: [OE-core] [PATCH 5/5] bluetooth.bbclass: set bluez5 as
> the default BT stack
>
> On 3 April 2015 at 15:13, Cristian Iorga <cristian.iorga@intel.com
> <mailto:cristian.iorga@intel.com>> wrote:
>
> -# Define a variable that expands to the recipe (package)
> providing core
> -# bluetooth support on the platform:
> +# Define a variable that expands to the recipe (package) providing
> +# core bluetooth support on the platform:
> # "" if bluetooth is not in DISTRO_FEATURES
> -# else "bluez5" if bluez5 is in DISTRO_FEATURES
> -# else "bluez4"
> +# else "bluez4" if bluez4 is in DISTRO_FEATURES
> +# else "bluez5"
>
>
> That wasn't the behaviour that 1.8 sets. We think we should continue
> to respect the bluez5 DISTRO_FEATURE and add it to
> DISTRO_FEATURES_BACKFILL.
>
> Ross
>
>
>
[-- Attachment #2: Type: text/html, Size: 6586 bytes --]
next prev parent reply other threads:[~2015-04-06 13:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 14:13 [PATCH 0/5] Switch to BlueZ 5.x as default Bluetooth stack Cristian Iorga
2015-04-03 14:13 ` [PATCH 1/5] bluez5: upgrade to 5.29 Cristian Iorga
2015-04-03 19:01 ` Jack Mitchell
2015-04-03 14:13 ` [PATCH 2/5] bluez: remove recipes collection Cristian Iorga
2015-04-03 14:13 ` [PATCH 3/5] maintainers.inc: remove info related to bluez4 Cristian Iorga
2015-04-03 14:13 ` [PATCH 4/5] upstream_tracking.inc: bluez4 removed from oe-core Cristian Iorga
2015-04-03 14:13 ` [PATCH 5/5] bluetooth.bbclass: set bluez5 as the default BT stack Cristian Iorga
2015-04-05 21:40 ` Burton, Ross
2015-04-06 7:31 ` Iorga, Cristian
2015-04-06 12:57 ` Peter A. Bigot [this message]
2015-04-06 13:18 ` Otavio Salvador
2015-04-06 14:32 ` Iorga, Cristian
2015-04-06 21:21 ` Peter A. Bigot
2015-04-06 21:39 ` Christopher Larson
2015-04-06 23:41 ` Peter A. Bigot
2015-04-14 13:28 ` Burton, Ross
2015-04-14 15:38 ` Christopher Larson
2015-04-15 15:05 ` Burton, Ross
2015-04-07 10:55 ` Martin Jansa
2015-04-07 11:21 ` Iorga, Cristian
2015-04-07 12:35 ` Martin Jansa
2015-04-07 10:27 ` Tanu Kaskinen
2015-04-07 11:23 ` Iorga, Cristian
2015-04-07 11:41 ` Tanu Kaskinen
2015-04-07 11:51 ` Iorga, Cristian
2015-04-07 12:36 ` Tanu Kaskinen
2015-04-07 12:44 ` Martin Jansa
2015-04-07 12:46 ` Tanu Kaskinen
2015-04-07 13:02 ` Martin Jansa
2015-04-07 20:16 ` Tanu Kaskinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552282D7.6040108@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox