From: "Fritz Code" <codefritz@googlemail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] different versions of bluez depending on distribution
Date: Sat, 14 Jun 2008 11:54:24 +0200 [thread overview]
Message-ID: <3e9cdced0806140254u1fdcc62dq4333252ba2d01662@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 746 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 854 bytes --]
[-- Attachment #2: Type: text/plain, Size: 247 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-06-14 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 9:54 Fritz Code [this message]
2008-06-18 10:29 ` [Bluez-users] different versions of bluez depending on distribution Stefan Seyfried
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=3e9cdced0806140254u1fdcc62dq4333252ba2d01662@mail.gmail.com \
--to=codefritz@googlemail.com \
--cc=bluez-users@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