Hello all, Judging from what I have read on mailing lists, there is a good chance a lot of components will be ready to switch to bluez5 in 6 months timeframe.
Regards, Cristian -----Original Message----- From: openembedded-core-boun...@lists.openembedded.org [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Burton, Ross Sent: Wednesday, March 13, 2013 6:20 PM To: Koen Kooi Cc: Martin Jansa; openembedded-core@lists.openembedded.org Subject: Re: [OE-core] [PATCH 2/2] bluez5: new package for v5.3 On 13 March 2013 02:14, Koen Kooi <k...@dominion.thruhere.net> wrote: > At the risk of sounding snarky while making a real recommendation: Why > not do it oe-core > style and completely remove bluez 4.x at the start > of the 1.5 cycle and work through the breakage? I guess that means I > volunteer to help with that :) Is the world going to migrate to the bluez5 API in six months? I was expecting to have to carry bluez4 and 5 for at least one or two cycles. We have a similar issue with GStreamer 0.10 and 1.0 - we could drop 0.10 and port what ships in oe-core, but the subsequent breakage would cause a riot. Ross _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
