From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4
Date: Tue, 05 Sep 2006 19:13:19 +0200 [thread overview]
Message-ID: <1157476399.5963.4.camel@localhost> (raw)
In-Reply-To: <20060905164657.GA16417@suse.de>
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.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-09-05 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060903124043.2028.48247.reportbug@forza>
[not found] ` <1157367160.32195.54.camel@aeonflux.holtmann.net>
[not found] ` <20060904100025.GA17058@esaurito.net>
[not found] ` <1157371912.32195.69.camel@aeonflux.holtmann.net>
2006-09-05 10:32 ` [Bluez-devel] Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4 Filippo Giunchedi
2006-09-05 11:07 ` Bug#385857: " Marcel Holtmann
2006-09-05 16:46 ` Stefan Seyfried
2006-09-05 17:13 ` Marcel Holtmann [this message]
2006-09-05 18:15 ` Stefan Seyfried
2006-09-05 18:59 ` Marcel Holtmann
2006-09-05 20:38 ` Stefan Seyfried
2006-09-05 21:08 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1157476399.5963.4.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.