From: Phil Blundell <pb@pbcl.net>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3 0/2] BlueZ 5 experimental recipes
Date: Tue, 16 Jul 2013 15:33:49 +0100 [thread overview]
Message-ID: <1373985229.2651.84.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1373984927-21039-1-git-send-email-cristian.iorga@intel.com>
On Tue, 2013-07-16 at 17:28 +0300, Cristian Iorga wrote:
> Observe my investigation below in order to decide if RREPLACES is needed.
> Conclusion: BlueZ 5.x will be eventually an upgrade path for an already installed
> embedded device. As such, RREPLACES is needed for a system-wide upgrade.
It wasn't very obvious to me that these results make a compelling case
for bluez4 needing to RREPLACE bluez5. Indeed, this section:
root@qemux86:~# opkg install bluez5
Multiple replacers for bluez5, using first one (bluez4).
Package bluez4 is already installed on root.
root@qemux86:~# opkg list-installed | grep bluez
bluez4 - 4.101-r6.0
libasound-module-bluez - 4.101-r6.0
... seems to illustrate (modulo the usual amount of opkg craziness) why
having it be so is not a very good thing.
p.
next prev parent reply other threads:[~2013-07-16 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 14:28 [PATCH V3 0/2] BlueZ 5 experimental recipes Cristian Iorga
2013-07-16 14:28 ` [PATCH V3 1/2] bluez5: new package for v5.7 Cristian Iorga
2013-07-16 14:28 ` [PATCH V3 2/2] bluez4: conflicts with/replaces bluez5 Cristian Iorga
2013-07-16 14:33 ` Phil Blundell [this message]
2013-07-16 14:36 ` [PATCH V3 0/2] BlueZ 5 experimental recipes Iorga, Cristian
2013-07-16 14:47 ` Saul Wold
2013-07-16 14:49 ` Iorga, Cristian
2013-07-16 14:55 ` Phil Blundell
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=1373985229.2651.84.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=cristian.iorga@intel.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