FYI: F20 Feature: Migrate to Bluez5
kalevlember at gmail.com
Fri Jun 21 15:16:09 UTC 2013
2013-05-06 11:13, Peter Robinson skrev:
> On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera <bnocera at redhat.com> wrote:
>> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
>> Bluez5 uses a D-Bus API that's not compatible with Bluez4 and as
>> such, management applications and a number of libraries and daemons will
>> need to be ported.
>> For GNOME 3.10 (due September 2013), Gustavo Padovan and I are going to
>> be porting gnome-bluetooth, NetworkManager and PulseAudio to BlueZ5.
>> Packages for BlueZ5 will be available as soon as we figure out how to
>> integrate a few downstream features that were in the Fedora packages.
>> Bluez4 and Bluez5 are not parallel-installable, and incompatible, so
>> other applications relying on Bluez4 will need to be ported by their
>> respective maintainers.
> Any analysis to what packages are affected, how many are yet to
> support the new API and how hard it will be for them to be ported
I took a look to see what the impact would be. I am not a BlueZ expert,
so Bastien, please correct me if I am wrong somewhere.
BlueZ ships a daemon and provides two main interfaces for applications
to use it:
1) libbluetooth shared library
2) org.bluez DBus API
The TL;DL version is that in my findings, the only package that still
needs porting to bluez 5 is blueman. Others should either just continue
working, or need new versions packaged up.
Applications that use the libbluetooth shared library
The library ABI hasn't changed and the soname in 5.x is still the same
as was in 4.x: libbluetooth.so.3, so the impact should be minimal.
Everything should be able to continue working without needing even a
$ repoquery -q --whatrequires bluez-libs -s | sort | uniq
Applications that use the org.bluez dbus API
The DBus service is shipped in the 'bluez' package and I assume all the
DBus API consumers have a dep on the 'bluez' package for that:
$ repoquery -q --whatrequires bluez -s | sort | uniq
I took a quick look at all the packages above and the following don't
seem to use the dbus API and have a dep on the 'bluez' package for other
reasons (use command line utilities etc.):
The following use the DBus API:
blueman [Status: needs porting to 5.x]
gnome-bluetooth [Status: ported]
libbluedevil [Status: port available in a git branch,
pulseaudio [Status: ported]
More information about the devel