public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 23:08:31 +0200	[thread overview]
Message-ID: <1157490511.5963.53.camel@localhost> (raw)
In-Reply-To: <20060905203814.GA4515@suse.de>

Hi Stefan,

> > Let me put it this way. The 3.0 announcement came with a clear warning
> > that the PIN helper is dead and we now need a default passkey agent for
> > every desktop. It was one reason why I jumped to next major number. I
> > don't do this without a serious reason. I provided an example of a
> > passkey agent and the Maemo guys implemented a passkey agent for their
> > platform, but nobody else seemed to care.
> 
> In the KDE case, i think that the kdebluetooth code is pretty much without
> an active maintainer. But i have a promising new talent at hand that will
> start fixing and bring it up to date :-)

sounds great. Please tell him that he should use the BlueZ D-Bus API
only. So a linking against libbluetooth is not an option anymore. This
will be the way we will go for the GNOME stuff, too.

Since I will travel tomorrow to Nuremberg for the Linux-Kongress, you
might wanna send him to my talk ;)

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

      reply	other threads:[~2006-09-05 21:08 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
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 [this message]

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=1157490511.5963.53.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox