Return-Path: Message-ID: <3e9cdced0806140254u1fdcc62dq4333252ba2d01662@mail.gmail.com> Date: Sat, 14 Jun 2008 11:54:24 +0200 From: "Fritz Code" To: bluez-users@lists.sourceforge.net MIME-Version: 1.0 Subject: [Bluez-users] different versions of bluez depending on distribution Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1122790467==" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net --===============1122790467== Content-Type: multipart/alternative; boundary="----=_Part_20723_29742513.1213437264448" ------=_Part_20723_29742513.1213437264448 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Well there seem to be different bluez versions depending on the distribution. E.g. on my (old) SuSE 10.2 System bluez is installed in version 3.7 (its supposed to be newer than the latest official bluez package - strange!) ? But the latest release of the public bluez.org download-section is 3.32? Do the the distributors compile their own bluez packages and at the same time change the version-number? I also figured out some differences e.g. in the arguments of the request message, sent out after a create_bonding. Why do they make such changes? I think this strategy is sort of confusing because you don't know exactly the differences of official bluez packages and the adpated of your distribution... Thanks... -- Regards, --Codefritz ------=_Part_20723_29742513.1213437264448 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Well there seem to be different bluez versions depending on the distribution. E.g. on my (old) SuSE 10.2 System bluez is installed in version 3.7 (its supposed to be newer than the latest official bluez package - strange!) ?
But the latest release of the public bluez.org download-section is 3.32?

Do the the distributors compile their own bluez packages and at the same time change the version-number?
I also figured out some differences e.g. in the arguments of the request message, sent out after a create_bonding.
Why do they make such changes?

I think this strategy is sort of confusing because you don't know exactly the differences of official bluez packages and the adpated of your distribution...

Thanks...


--
Regards,
--Codefritz



------=_Part_20723_29742513.1213437264448-- --===============1122790467== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php --===============1122790467== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users --===============1122790467==--