Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: "Iorga, Cristian" <cristian.iorga@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3 0/2] BlueZ 5 experimental recipes
Date: Tue, 16 Jul 2013 15:55:10 +0100	[thread overview]
Message-ID: <1373986510.2651.87.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB16C05A76@IRSMSX105.ger.corp.intel.com>

On Tue, 2013-07-16 at 14:36 +0000, Iorga, Cristian wrote:
> " why having it be so is not a very good thing."
> 
> Sorry, I did not understood this part.
> 
> Judging by my investigation, is RREPLACES needed or not?

I don't believe there is any justification for making bluez4 Replace:
bluez5.

I think you could possibly make an argument that having bluez5 Replace:
bluez4 might be a good thing, although given the way opkg behaves with
them I'm not entirely convinced.  Personally I would say that there
should be no replacing here.

p.




      parent reply	other threads:[~2013-07-16 14:55 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 ` [PATCH V3 0/2] BlueZ 5 experimental recipes Phil Blundell
2013-07-16 14:36   ` Iorga, Cristian
2013-07-16 14:47     ` Saul Wold
2013-07-16 14:49       ` Iorga, Cristian
2013-07-16 14:55     ` Phil Blundell [this message]

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=1373986510.2651.87.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