From patchwork Wed Mar 13 04:42:38 2013
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [V2,3/4] bluez5: conflicts with bluez4
Date: Wed, 13 Mar 2013 04:42:38 -0000
From: Ross Burton <ross.burton@intel.com>
X-Patchwork-Id: 46109
Message-Id: <CAJTo0LYBe10HhsMtynzpuS5arEDtXBFxcLKqryPFWEV=7Q7SbQ@mail.gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org

But bluez4 doesn't provide bluez5 and vice versa - the runtime API are
different.

Ross


diff --git a/meta/recipes-connectivity/bluez5/bluez5_5.3.bbb/meta/recipes-connectivity/bluez5/
bluez5_5.3.bb
index 311562f..5963483 100644
--- a/meta/recipes-connectivity/bluez5/bluez5_5.3.bb
+++ b/meta/recipes-connectivity/bluez5/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.