From: "Peter A. Bigot" <pab@pabigot.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC 00/10] mods to support virtual/bluez
Date: Mon, 10 Nov 2014 15:16:19 -0600 [thread overview]
Message-ID: <cover.1415650249.git.pab@pabigot.com> (raw)
This series is a proposed fix for Yocto 5031, providing virtual/bluez to
select between bluez4 and bluez5. The intent is to continue using
bluez4 as the default, but to allow distros to switch to bluez5 if the
packages they need support the new interface.
The material here depends on this RFC branch:
git://git.yoctoproject.org/poky-contrib pabigot/wip/virtual-bluez
Please comment on the overall approach in the oe-core thread.
The following changes since commit dac2422f737c351c37a8405a76b5f0b5df9311a0:
krb5: add initscripts-functions to RDEPENDS (2014-11-07 15:06:22 +0100)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded-contrib pabigot/wip/virtual-bluez
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=pabigot/wip/virtual-bluez
Peter A. Bigot (10):
gypsy: switch to virtual/bluez
gpsd: switch to virtual/bluez
foxtrotgps: switch to virtual/bluez
packagegroup-basic: switch bluetooth to virtual/bluez
gvfs: switch to virtual/bluez
obexd: conflict with bluez5
gnome-bluetooth: switch to virtual/bluez
gnokii: switch to virtual/bluez
obex-data-server: conflict with bluez5
openobex: switch to virtual/bluez
meta-gnome/recipes-connectivity/obex/obexd_0.48.bb | 2 ++
meta-gnome/recipes-gnome/gnome-bluetooth/gnome-bluetooth_2.32.0.bb | 5 +++--
meta-gnome/recipes-gnome/gvfs/gvfs_1.10.1.bb | 2 +-
meta-oe/recipes-connectivity/gnokii/gnokii_0.6.31.bb | 2 +-
meta-oe/recipes-connectivity/obex/obex-data-server_0.4.6.bb | 1 +
meta-oe/recipes-connectivity/obex/openobex_1.5.bb | 2 +-
meta-oe/recipes-core/packagegroups/packagegroup-basic.bb | 2 +-
meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb | 2 +-
meta-oe/recipes-navigation/gpsd/gpsd_3.10.bb | 2 +-
meta-oe/recipes-navigation/gypsy/gypsy.inc | 2 +-
10 files changed, 13 insertions(+), 9 deletions(-)
--
1.8.5.5
next reply other threads:[~2014-11-10 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 21:16 Peter A. Bigot [this message]
2014-11-10 21:16 ` [RFC 01/10] gypsy: switch to virtual/bluez Peter A. Bigot
2014-11-10 21:16 ` [RFC 02/10] gpsd: " Peter A. Bigot
2014-11-10 21:16 ` [RFC 03/10] foxtrotgps: " Peter A. Bigot
2014-11-10 21:16 ` [RFC 04/10] packagegroup-basic: switch bluetooth " Peter A. Bigot
2014-11-10 21:16 ` [meta-gnome][RFC 05/10] gvfs: switch " Peter A. Bigot
2014-11-10 21:16 ` [meta-gnome][RFC 06/10] obexd: conflict with bluez5 Peter A. Bigot
2014-11-10 21:16 ` [meta-gnome][RFC 07/10] gnome-bluetooth: switch to virtual/bluez Peter A. Bigot
2014-11-10 21:16 ` [RFC 08/10] gnokii: " Peter A. Bigot
2014-11-10 21:16 ` [RFC 09/10] obex-data-server: conflict with bluez5 Peter A. Bigot
2014-11-10 21:16 ` [RFC 10/10] openobex: switch to virtual/bluez Peter A. Bigot
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=cover.1415650249.git.pab@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-devel@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