On 12 March 2013 08:13, Burton, Ross wrote:
>> Now they need to refine RREPLACES/RCONFLICTS/RPROVIDES combo in distro
>> config too when they do explicit decision to change bluez version.
>
> Yes, so bluez4 and bluez5 should explicitly conflict each other. This
> should be be done.
Chatted with
On Wed, 2013-03-13 at 10:14 +0100, Koen Kooi wrote:
> Op 12 mrt. 2013, om 16:13 heeft "Burton, Ross" het
> volgende geschreven:
>
> > On 12 March 2013 03:07, Martin Jansa wrote:
> >>> You can't just upgrade from bluez4 to bluez5 like you'd upgrade from
> >>> glib 2.10 to glib 2.12 - the API was
...@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 wrote:
> At the risk of sound
On 13 March 2013 02:14, Koen Kooi 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
Op 12 mrt. 2013, om 16:13 heeft "Burton, Ross" het
volgende geschreven:
> On 12 March 2013 03:07, Martin Jansa wrote:
>>> You can't just upgrade from bluez4 to bluez5 like you'd upgrade from
>>> glib 2.10 to glib 2.12 - the API was totally rewritten and the reason
>>> that we're maintaining bo
On 12 March 2013 03:07, Martin Jansa wrote:
>> You can't just upgrade from bluez4 to bluez5 like you'd upgrade from
>> glib 2.10 to glib 2.12 - the API was totally rewritten and the reason
>> that we're maintaining both is because removing bluez4 would mean
>> removing bluetooth support is most of
On Tue, Mar 12, 2013 at 02:24:30AM -0700, Burton, Ross wrote:
> Hi Martin,
Hi Ross,
> On 12 March 2013 00:00, Martin Jansa wrote:
> > And is that correct? I guess some files on target will conflict between
> > bluez4 and bluez5, so how is user/distro supposed to upgrade from 4 to
> > 5?
>
> You
Hi Martin,
On 12 March 2013 00:00, Martin Jansa wrote:
> And is that correct? I guess some files on target will conflict between
> bluez4 and bluez5, so how is user/distro supposed to upgrade from 4 to
> 5?
You can't just upgrade from bluez4 to bluez5 like you'd upgrade from
glib 2.10 to glib 2.
iginal Message-
> From: Martin Jansa [mailto:martin.ja...@gmail.com]
> Sent: Tuesday, March 12, 2013 9:01 AM
> To: Iorga, Cristian
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 2/2] bluez5: new package for v5.3
>
> On Mon, Mar 11, 2013 at 03:
uot; in the beginning would be nice, also. Thanks.
-Original Message-
From: Martin Jansa [mailto:martin.ja...@gmail.com]
Sent: Tuesday, March 12, 2013 9:01 AM
To: Iorga, Cristian
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] bluez5: new package for v5.3
On Mon, Mar 11, 2013 at 03:56:49PM +0200, Cristian Iorga wrote:
> - bluez5 does not replace bluez4
And is that correct? I guess some files on target will conflict between
bluez4 and bluez5, so how is user/distro supposed to upgrade from 4 to
5?
Why not move to bluez PN and set R* variables to do
- bluez5 does not replace bluez4
- bluez5 is integrated with systemd
Signed-off-by: Cristian Iorga
---
.../bluez5/bluez5-5.3/bluetooth.conf | 16 +++
.../bluez5/bluez5-5.3/fix-udev-paths.patch | 35 +++
meta/recipes-connectivity/bluez5/bluez5.inc
12 matches
Mail list logo
