Description of problem: I'm trying to fast-track the submission of kdebluetooth into KDE/F7. Unlike it's counter-part, kdebluetooth doesn't include new-style DBUS based kdepin and require old-style pin helper. While upstream is working on a DBUS-enabled version, I doubt that it'll be ready before KDE4/F8. The attached patch [1] was made by one of the kdebluetooth and 'seems' to work just fine with kdebluetotho -without- breaking bluez-utils-gnome. This patch also adds passkey-agent. [1] http://www.kmobiletools.org/files/bluez-pin-exec-patch-r3.diff.bz2
Created attachment 152670 [details] old-style pin-helper patch
Created attachment 152671 [details] bluez-utils spec patch. Just for reference, bluez-utils.spec.patch. (What I used for testing under both GNOME and KDE)
FYI, I saw references to this patch in Debian, Ubunutu, Manriva, etc. I have no idea if anyone is actually using it. - Gilboa
I would normally suggest that if you can't just fix your package to keep up, then you aren't qualified as a package maintainer. But then again, this is DBus. So maybe I can have sympathy. I don't really consider myself qualified to maintain the bluez-utils package these days either, because of its extensive use of DBus. Deferring to Marcel...
Sorry for the late reply. A. Given the time constraint (F7 is just around the corner, F7/KDE requires this functionality), being an out-sider (I'm not a member of the kdebluetooth tema), I doubt that it'll be possible for me to hack and test kdebluetooth fast enough to get it accepted on time. B. kdebluetooth team -is- working on a DBUS patch for KDE4 that will eventually be back-ported to KDE 3.5.x. There's no use to doing things twice. (Again, given the fact that there's a working patch) On a side note, not all packagers are programmers. While I am, limiting Fedora maintainer ranks to seasoned programmers only doesn't strike me a wise choice. - Gilboa
BTW, I may retire this patch request. If all goes well, I should have a working wrapper next week. (I'm still struggling with the lack of documentation on bluez-utils-dbus interface. If it works, it should be sufficient to keep kdebluetooth working until kdebluetooth + qt-dbus combo will be released. - Gilboa
OK. The wrapper seems to be working. I'm currently looking to get it included upstream into bluez-utils. (The wrapper is rather generic - it can also support script tools such as dialog and zenity.) In short, this RFE can be closed. Should I do it myself? - Gilboa
Closed.