Re: [Bluez-devel] Suggesting bluez_pinhelper

Gilboa Davara
2007-05-27T18:41:40Z

On 5/27/07, Petteri R=E4ty <betelgeuse@gentoo.org> wrote:
> Gilboa Davara kirjoitti:
> > AFAIK there are 3 possibles solutions to this problem.
> > A. Patch bluez-utils' passkey-agent (adding old-style passkey support)
> > B. Use the un-official (?) SUSE patch that adds DBUS support to
> > kdebluetooth.
> > C. Keep kdebluetooth and bluez-utils as they are and create an out-side
> > wrapper.
> >
> > Do you have any idea which course Gentoo used?
> >
> > - Gilboa
> >
>
> http://viewcvs.gentoo.org/viewcvs.py/gentoo-x86/net-wireless/kdebluetooth=
/kdebluetooth-1.0_beta2-r2.ebuild?rev=3D1.1&view=3Dlog
>

A short comment about the OpenSUSE patch.
Unless Gentoo's kdebluetooth maintainer is QT/KDE/CPP programmer, he's
taking an unreasonable risk.
If I'm using a wrapper and something breaks, it's either in the
wrapper code (and I'm the one to blame) or in kdebluetooth (which can
be reported upstream to kmobiletools).
... But if an unsupported patch is used, you're S.O.L.
You can't report the bug upstream (not their code) and you can't
report the bug to SUSE people. (Not their distro)
In short, you get to keep all the broken pieces....

- Gilboa