Hello -- I have a question about linking non-GPL code to BlueZ. This is
very much along the lines of the previous conversation at=20
http://thread.gmane.org/gmane.linux.bluez.devel/2444 -- the quick
summary of which is:=20
=20
Marcel: Date: 2004-06-28 14:48:48 GMT: "For the BlueZ library and the
utilities we can talk about it. Some time ago people asked for a LGPL
version of the library and actually I tend to agree with that. However
this can't be decided by me alone, because part of the code is copyright
by Qualcomm and also by Maxim Krasnyansky himself. For the utilities I
don't see any need for a different license. I believe in the GPL and
from my view releasing the Linux Bluetooth library under LGPL is the
only step I wanna make forward to allow closed source products based on
BlueZ."
Is this still the current status of GPL/LGPL for the BlueZ libraries
(libbluetooth.so) -- or has there been an update (I haven't found
anything more recent on the mailing list about this).
What is the recommended way to write a non-GPL application on top of
BlueZ, or is this not currently allowed...? My understanding is that it
is OK to use the linux kernel syscall interface from non-GPL code, but
that this would not extend to libbluetooth.so...
Cheers,
Trevor
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Fredy P wrote:
> El mi?, 01-06-2005 a las 23:44 +0200, Marcel Holtmann escribi?:
[...]
>>>Is this still the current status of GPL/LGPL for the BlueZ libraries
>>>(libbluetooth.so) -- or has there been an update (I haven't found
>>>anything more recent on the mailing list about this).
>>nothing has changed at the moment. Ask Max for an update of changing the
>>BlueZ library from GPL to LGPL.
> For the free software and open source interest is not good idea change
> GPL to LGPL, can read this:
> http://www.gnu.org/licenses/why-not-lgpl.html
This debate is almost as old as the free software movement or the
introduction of the LGPL respectively.
The question is what you intend to achieve by putting sourcecode under
the GPL or LGPL.
Concerning libbluetooth I would strongly and also urgently propose to
put it under LGPL for several reasons.
First of all is that libbluetooth is part of BlueZ which is the official
Bluetooth stack for Linux. It should not limit the use of Linux in any
way. The limiting factor here is that GPL on a library renders all
programs that use it into GPL. For commercial software vendors this is a
no-go.
Yes, in an ideal world we would not care much but our world is far from
being ideal and currently I would strongly prefer wide use of Linux than
limiting the use.
LGPL on the library itself assures that the lib will remain free and
that changes to it will be put back into it. For a library there is no
need to be GPL. It simply limits its use which is not good.
So please yes, try to get hold of Max and ask for his permission...
Regards
nils faerber
- --
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCn1YFJXeIURG1qHgRArjkAJ9efx3jQrLt9O2Znj46BavwZzK0SQCfU4uL
fKg+pkeilCsGJKX7BXSkWro=
=IJkL
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
El mi=E9, 01-06-2005 a las 23:44 +0200, Marcel Holtmann escribi=F3:
> Hi Trevor,
>=20
> > I have a question about linking non-GPL code to BlueZ. This is
> > very much along the lines of the previous conversation at=20
> > http://thread.gmane.org/gmane.linux.bluez.devel/2444 -- the quick
> > summary of which is:=20
> > =20
> > Marcel: Date: 2004-06-28 14:48:48 GMT: "For the BlueZ library and the
> > utilities we can talk about it. Some time ago people asked for a LGPL
> > version of the library and actually I tend to agree with that. However
> > this can't be decided by me alone, because part of the code is copyrigh=
t
> > by Qualcomm and also by Maxim Krasnyansky himself. For the utilities I
> > don't see any need for a different license. I believe in the GPL and
> > from my view releasing the Linux Bluetooth library under LGPL is the
> > only step I wanna make forward to allow closed source products based on
> > BlueZ."
> >=20
> > Is this still the current status of GPL/LGPL for the BlueZ libraries
> > (libbluetooth.so) -- or has there been an update (I haven't found
> > anything more recent on the mailing list about this).
>=20
> nothing has changed at the moment. Ask Max for an update of changing the
> BlueZ library from GPL to LGPL.
For the free software and open source interest is not good idea change
GPL to LGPL, can read this:
http://www.gnu.org/licenses/why-not-lgpl.html
>=20
> > What is the recommended way to write a non-GPL application on top of
> > BlueZ, or is this not currently allowed...? My understanding is that it
> > is OK to use the linux kernel syscall interface from non-GPL code, but
> > that this would not extend to libbluetooth.so...
>=20
> Actually I disagree with the non-GPL use of the syscall interface, but I
> am not lawyer. From my understanding all the bluetooth/*.h include files
> are GPL and you need them for your application. You can't replace them
> without ending up in derived work.
>=20
> Regards
>=20
> Marcel
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=3Doffad-ysdn-ostg-q22=
005
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Trevor,
> I have a question about linking non-GPL code to BlueZ. This is
> very much along the lines of the previous conversation at
> http://thread.gmane.org/gmane.linux.bluez.devel/2444 -- the quick
> summary of which is:
>
> Marcel: Date: 2004-06-28 14:48:48 GMT: "For the BlueZ library and the
> utilities we can talk about it. Some time ago people asked for a LGPL
> version of the library and actually I tend to agree with that. However
> this can't be decided by me alone, because part of the code is copyright
> by Qualcomm and also by Maxim Krasnyansky himself. For the utilities I
> don't see any need for a different license. I believe in the GPL and
> from my view releasing the Linux Bluetooth library under LGPL is the
> only step I wanna make forward to allow closed source products based on
> BlueZ."
>
> Is this still the current status of GPL/LGPL for the BlueZ libraries
> (libbluetooth.so) -- or has there been an update (I haven't found
> anything more recent on the mailing list about this).
nothing has changed at the moment. Ask Max for an update of changing the
BlueZ library from GPL to LGPL.
> What is the recommended way to write a non-GPL application on top of
> BlueZ, or is this not currently allowed...? My understanding is that it
> is OK to use the linux kernel syscall interface from non-GPL code, but
> that this would not extend to libbluetooth.so...
Actually I disagree with the non-GPL use of the syscall interface, but I
am not lawyer. From my understanding all the bluetooth/*.h include files
are GPL and you need them for your application. You can't replace them
without ending up in derived work.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users