From: Saul Wold <sgw@linux.intel.com>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V4 0/2] BlueZ 5 experimental recipes
Date: Wed, 17 Jul 2013 15:29:06 -0700 [thread overview]
Message-ID: <51E71AB2.7030209@linux.intel.com> (raw)
In-Reply-To: <1373988362-10097-1-git-send-email-cristian.iorga@intel.com>
On 07/16/2013 08:26 AM, Cristian Iorga wrote:
> This sets of patches adds bluez5 recipes as experimental packages.
> BlueZ 5.X is not an upgrade for Bluez 4.x, as such, no upgrade is
> provided/possible.
> The two versions of the BT stack also conflicts each other.
>
> In V4 RREPLACES is removed from the recipes.
>
> Cristian Iorga (2):
> bluez5: new package for v5.7
> bluez4: conflicts with bluez5
>
> meta/recipes-connectivity/bluez/bluez4_4.101.bb | 2 +
> .../bluez5/bluez5-5.7/bluetooth.conf | 16 +++++
> meta/recipes-connectivity/bluez5/bluez5.inc | 68 ++++++++++++++++++++
> meta/recipes-connectivity/bluez5/bluez5_5.7.bb | 5 ++
> 4 files changed, 91 insertions(+)
> create mode 100644 meta/recipes-connectivity/bluez5/bluez5-5.7/bluetooth.conf
> create mode 100644 meta/recipes-connectivity/bluez5/bluez5.inc
> create mode 100644 meta/recipes-connectivity/bluez5/bluez5_5.7.bb
>
Have both recipes in a world build causes the following WARNING:
NOTE: multiple providers are available for runtime
libasound-module-bluez (bluez4, bluez5)
NOTE: consider defining a PREFERRED_PROVIDER entry to match
libasound-module-bluez
You can add a line in meta/conf/distro/include/default-providers.inc
Sau!
next prev parent reply other threads:[~2013-07-17 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 15:26 [PATCH V4 0/2] BlueZ 5 experimental recipes Cristian Iorga
2013-07-16 15:26 ` [PATCH V4 1/2] bluez5: new package for v5.7 Cristian Iorga
2013-07-16 15:26 ` [PATCH V4 2/2] bluez4: conflicts with bluez5 Cristian Iorga
2013-07-16 18:22 ` [PATCH V4 0/2] BlueZ 5 experimental recipes Burton, Ross
2013-07-17 22:29 ` Saul Wold [this message]
2013-07-18 6:08 ` Saul Wold
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=51E71AB2.7030209@linux.intel.com \
--to=sgw@linux.intel.com \
--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