[CC’ing linux-bluetooth, maybe you can tell us what’s happening]
Hi,
Am Sonntag, den 07.09.2008, 12:43 +0200 schrieb Filippo Giunchedi:
> On Sun, Sep 07, 2008 at 11:50:12AM +0200, Joachim Breitner wrote:
> > > that explains the bug, unless I'm missing something of course :)
> >
> > it does indeed, but then I wonder why this functionality is present in
> > an openembedded based image for the FreeRunner that runs (supposedly)
> > bluez-utils 3.23-r2, which is older than what’s in Debian, and I can not
> > find any patches regarding this...
> >
> > And indeed, looking at:
> > http://shr.bearstech.com/sources/bluez-utils-3.23.tar.gz
> > The above code lines are filled with some functionality!
> >
> > So looking in the changelog, I see:
> > ver 3.32:
> > [..]
> > Remove HAL support helpers.
> > Remove inotify support.
> > Remove service daemon activation handling.
> > Remove uneeded D-Bus API extension.
> >
> > Interesting. Do you have any idea why this was removed? Is there some
> > replacement functionality?
>
> Judging from the code above my first guess (offhand) is because services migrated
> from external processes to plugins (loaded via g_module_load).
>
> Unfortunately I'm unaware of any replacement (though I have not checked the new
> 4.x code)
I’m not sure. I think the dbus interface already is part of the new
plugin based stuff? Also, if I disable the plugin (DisablePlugins=input
in /etc/bluetooth/main.conf), the whole /org/bluez/service_input dbus
interface disappears.
The relevant diff in upstream’s CVS does unfortunately not tell us more
about why this was removed:
http://bluez.cvs.sourceforge.net/bluez/utils/hcid/dbus-service.c?r1=1.151&r2=1.152
So I CC’ed upstream: Would you please explain us why this dbus interface
was disabled, and what’s supposed to replace it?
Thanks everyone,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
[email protected] | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: [email protected] | http://people.debian.org/~nomeata