From: Marcel Holtmann <marcel@holtmann.org>
To: Madhavi Manchala <madhavi.linux@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Question about BlueZ licenses (LGPL and Apache)
Date: Sat, 07 Aug 2010 07:07:00 +0200 [thread overview]
Message-ID: <1281157620.12579.157.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimiBsL60-8w4MPoP=g8Fo_+U-SrSBTa9--aqEK4@mail.gmail.com>
Hi Madhavi,
> I am trying to implement a custom voice codec on the android bluetooth
> platform by linking it, into the A2DP module. I have heard different
> versions from different people regarding the licenses (like LGPL and
> Apache License). So, before starting my work, I would like to know if
> I would be forced to reveal my source code, once I implement my codec
> on BlueZ stack. Please let me know, so that I can choose my platform,
> before starting my work.
BlueZ (bluetoothd and libbluetooth) is licensed under GPL 2.0 license
and nothing else. It is pretty clear in the COPYING file. There are a
few source code files licensed under LGPL, but after linking the end
result is still GPL. If in doubt ask your lawyer since nobody here on
the mailing list can give you official legal advise.
Regards
Marcel
next prev parent reply other threads:[~2010-08-07 5:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 15:44 Question about BlueZ licenses (LGPL and Apache) Madhavi Manchala
2010-08-07 5:07 ` Marcel Holtmann [this message]
2010-08-07 13:28 ` Alan Carvalho de Assis
2010-08-09 7:38 ` Madhavi Manchala
2010-08-09 11:02 ` Siarhei Siamashka
2010-08-09 9:28 ` Madhavi Manchala
2010-08-09 9:31 ` Luiz Augusto von Dentz
2010-08-09 19:37 ` Pavan Savoy
2010-08-10 7:49 ` Luiz Augusto von Dentz
2010-08-10 15:14 ` Pavan Savoy
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=1281157620.12579.157.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=madhavi.linux@gmail.com \
/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