Return-Path: Message-ID: <4659C461.8070405@gentoo.org> Date: Sun, 27 May 2007 20:48:17 +0300 From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= MIME-Version: 1.0 To: gilboad@gmail.com, BlueZ development References: <1180273950.15368.42.camel@gilboa-work-dev.localdomain> <4659B8EC.3050708@gentoo.org> <1180287117.30116.17.camel@gilboa-work-dev.localdomain> In-Reply-To: <1180287117.30116.17.camel@gilboa-work-dev.localdomain> Subject: Re: [Bluez-devel] Suggesting bluez_pinhelper Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net 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=1.1&view=log ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel