From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Greylist: delayed 428 seconds by postgrey-1.34 at layers.openembedded.org; Mon, 06 Apr 2015 13:05:05 UTC Received: from p3plsmtpa07-01.prod.phx3.secureserver.net (p3plsmtpa07-01.prod.phx3.secureserver.net [173.201.192.230]) by mail.openembedded.org (Postfix) with ESMTP id 64C0B605D2 for ; Mon, 6 Apr 2015 13:05:05 +0000 (UTC) Received: from [192.168.65.10] ([75.72.225.8]) by p3plsmtpa07-01.prod.phx3.secureserver.net with id Ccxx1q00G0BVjqb01cxyAL; Mon, 06 Apr 2015 05:57:58 -0700 Message-ID: <552282D7.6040108@pabigot.com> Date: Mon, 06 Apr 2015 07:57:59 -0500 From: "Peter A. Bigot" Organization: Peter Bigot Consulting, LLC User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: openembedded-core@lists.openembedded.org References: <90c0094bfd5455dd40933ad4322e4c53adcd3147.1428070227.git.cristian.iorga@intel.com> <969F26A8BAB325438E7EB80D3C3134FB2F4944D2@irsmsx105.ger.corp.intel.com> In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB2F4944D2@irsmsx105.ger.corp.intel.com> Subject: Re: [PATCH 5/5] bluetooth.bbclass: set bluez5 as the default BT stack X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2015 13:05:07 -0000 Content-Type: multipart/alternative; boundary="------------010105000406060308010606" --------------010105000406060308010606 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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 > 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 > > > --------------010105000406060308010606 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit
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> 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




--------------010105000406060308010606--