[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: find_lang (kdebluetooth review)
- From: livinded <livinded deadbytes net>
- To: Discussion related to Fedora Extras <fedora-extras-list redhat com>
- Subject: Re: find_lang (kdebluetooth review)
- Date: Wed, 04 Apr 2007 10:14:51 -0700
Gilboa Davara wrote:
> On Wed, 2007-04-04 at 10:05 -0400, Matthew Miller wrote:
>> On Wed, Apr 04, 2007 at 03:11:12PM +0300, Gilboa Davara wrote:
>>> In general, there's one blocking issue with getting it out - kdepin:
>>> It seems that new(er) versions of bluez-utils no longer supports older
>>> pin-helpers - relaying instead on DBUS notifications and as such,
>>> bluez-utils must be patched in-order to support the old(er) dbus-less
>>> kdebluetooth.
>>> Once I'll get F7T3 running, I'll create a patched version of bluez-utils
>>> - and if it works, submit the patch to the upstream maintainer.
>>>
>> Wouldn't the more useful patch update kdebluetooth to use dbus?
>>
>>
>
> Yes it would - by far.
> But considering how close T4 is, I doubt that I'll have sufficient time
> to either port the kdebluetooth/KDE DBUS support to 3.5.x (is it even
> possible?) or add DBUS support for kdepin from scratch. (I'm the
> packager - not the original upstream developer so I'll need to know my
> way around the code first)
>
> AFAICS, the patch itself [1] looks reasonable enough.
> However, I want to test it with both kdebluetooth and bluez-gnome don't
> kick the bucket on this one.
>
> - Gilboa
> [1] http://www.kmobiletools.org/node/228
>
>
The developers of kdebluetooth say that with the release of KDE4 with
they plan on rewriting it with dbus support to get it working again with
the BlueZ-3.x branch and take advantage of KDE being written to have
dbus support.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]