Re: [Bluez-devel] Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4

Marcel Holtmann
2006-09-05T17:13:19Z

Hi Stefan,

> > > - I will add to bluez-utils a default non-interactive passkey agent (more or less
> > > like now but less hackish) which uses /etc/bluetooth/passkeys/<bt_addr> like
> > > now
> >
> > Doesn't make sense, because it is distro specific and you duplicate
> > functionality that is already present. Don't do this. This stuff must
> > die. I am serious about it.
>
> JFYI, i packaged the passkey-agent as-is for openSUSE factory and added a
> README, so the users can authenticate at all until the Desktop environments
> are ready. It might make sense to keep it IMO for all those people that do
> neither use gnome nor kde and still want to occasionally pair a rfcomm device,
> but maybe a multitude of easy to use passkey agents will pop up soon and
> we will have one for every taste :-)

my advise would be to include passkey-agent.c in the docs section as an
example. This is how other packages do it and to make this really clear,
the passkey-agent.c is an example. It is _NOT_ meant for any regular
installation. This is the reason why it is marked as noinst_*.

If something is marked as noinst_* in bluez-utils, then it is either an
example, not ready yet or to risky for installation. If you can't get it
installed with a configure option, then it is _NOT_ meant to be.