From: Saul Wold <sgw@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Martin Jansa <martin.jansa@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 3/4] bluez5: conflicts with bluez4
Date: Fri, 22 Mar 2013 14:23:29 -0700 [thread overview]
Message-ID: <514CCBD1.7060306@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYBe10HhsMtynzpuS5arEDtXBFxcLKqryPFWEV=7Q7SbQ@mail.gmail.com>
On 03/12/2013 09:42 PM, Burton, Ross wrote:
> But bluez4 doesn't provide bluez5 and vice versa - the runtime API are
> different.
>
Is there going to be a v3 version that has RREPLACES since they can not
co-exisit, but they also don't PROVIDE. As Ross pointed out in a
previous email, the package manager needs to be able to remove the older
bluez package when migrating from 4 -> 5.
Thanks
Sau!
> Ross
> --
> Ross Burton
> Sent with Sparrow <http://www.sparrowmailapp.com/?sig>
>
> On Tuesday, 12 March 2013 at 14:48, Martin Jansa wrote:
>
>> On Tue, Mar 12, 2013 at 07:03:14PM +0200, Cristian Iorga wrote:
>>> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com
>>> <mailto:cristian.iorga@intel.com>>
>>> ---
>>> meta/recipes-connectivity/bluez5/bluez5_5.3.bb <http://bluez5_5.3.bb>
>>> | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/meta/recipes-connectivity/bluez5/bluez5_5.3.bb
>>> <http://bluez5_5.3.bb>
>>> b/meta/recipes-connectivity/bluez5/bluez5_5.3.bb <http://bluez5_5.3.bb>
>>> index 311562f..5963483 100644
>>> --- a/meta/recipes-connectivity/bluez5/bluez5_5.3.bb
>>> <http://bluez5_5.3.bb>
>>> +++ b/meta/recipes-connectivity/bluez5/bluez5_5.3.bb
>>> <http://bluez5_5.3.bb>
>>> @@ -6,6 +6,8 @@ SRC_URI += "file://bluetooth.conf \
>>> SRC_URI[md5sum] = "44de20f6422bf90a01b8df48e7dfe4ed"
>>> SRC_URI[sha256sum] =
>>> "828e2cd1109835c2fc1d731fb7fd7b46951044e451cc8556a37e1312d8c8c9a6"
>>> +RCONFLICTS_${PN} = "bluez4"
>>
>> That's not enough for upgrade path, add RREPLACES/RPROVIDES too.
>>> +
>>> do_install_append() {
>>> install -d ${D}${sysconfdir}/bluetooth/
>>> install -m 0644 ${S}/profiles/audio/audio.conf
>>> ${D}/${sysconfdir}/bluetooth/
>>> --
>>> 1.7.10.4
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> <mailto:Openembedded-core@lists.openembedded.org>
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>> --
>> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>> <mailto:Martin.Jansa@gmail.com>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> <mailto: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
>
next prev parent reply other threads:[~2013-03-22 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 17:03 [PATCH V2 0/4] BlueZ 5.3 new package Cristian Iorga
2013-03-12 17:03 ` [PATCH V2 1/4] libical: add recipe back in oe-core Cristian Iorga
2013-03-12 17:03 ` [PATCH V2 2/4] bluez5: new package for v5.3 Cristian Iorga
2013-03-12 17:03 ` [PATCH V2 3/4] bluez5: conflicts with bluez4 Cristian Iorga
2013-03-12 21:48 ` Martin Jansa
2013-03-13 4:42 ` Burton, Ross
2013-03-22 21:23 ` Saul Wold [this message]
2013-03-12 17:03 ` [PATCH V2 4/4] bluez4: conflicts with bluez5 Cristian Iorga
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=514CCBD1.7060306@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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