From: Pierre-Yves Paulus <py@idlum.be>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] BlueZ and licensing issues
Date: Fri, 23 Jun 2006 08:58:27 +0200 [thread overview]
Message-ID: <1151045907.1450.73.camel@localhost> (raw)
Hello,
>>From the informations I was able to gather, up to today, everything
released by the BlueZ project has been released under the GPL, and
they're discussion about a LGPL release of bluez-libs in the future, if
Qualcomm does agree with that as one of the copyright holders.
My question: has BlueZ ever released to a person or a company a copy of
bluez-libs under another license than the GPL? It seems that they're
companies around (at least one I know of) that are distributing/selling
products linked against the libs (according to ldd), under a very
proprietary license - nothing looking like the GPL, and not accompanied
by the required notices and source code offerings. I'm wondering if some
have been granted an "exception" allowing them to do so legally.
Is it right that to date, the only way to use BlueZ in a non-GPL
licensed project is to communicate with it through some kind of IPC
(like TomTom did with their TTMP lib, or now with the dbus API exposed
by hcid)?
I'm trying to clearly understand the situation from the licensing point
of view, for possible use of BlueZ in a non-GPL project, thus those
questions. Any useful comment on that matter would be much appreciated.
Best Regards,
Pierre-Yves Paulus
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 reply other threads:[~2006-06-23 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 6:58 Pierre-Yves Paulus [this message]
2006-06-23 8:08 ` [Bluez-devel] BlueZ and licensing issues 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=1151045907.1450.73.camel@localhost \
--to=py@idlum.be \
--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;
as well as URLs for NNTP newsgroup(s).