All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Linking to BlueZ from non-GPL code
Date: Thu, 02 Jun 2005 20:55:01 +0200	[thread overview]
Message-ID: <429F5605.2070705@kernelconcepts.de> (raw)
In-Reply-To: <1117688464.3908.6.camel@localhost.localdomain>

-----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
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-06-02 18:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 21:33 [Bluez-users] Linking to BlueZ from non-GPL code Pering, Trevor
2005-06-01 21:44 ` Marcel Holtmann
2005-06-02  5:01   ` Fredy P
2005-06-02 18:55     ` Nils Faerber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-01 22:17 Pering, Trevor
2005-06-01 22:48 ` Marcel Holtmann
2005-06-02 10:01 ` Marco Trudel
2005-06-01 23:43 Pering, Trevor
2005-06-02  0:14 ` Brad Midgley
2005-06-02  9:57   ` Marco Trudel
2005-06-02 10:10     ` Marcel Holtmann
2005-06-02  0:19 ` 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=429F5605.2070705@kernelconcepts.de \
    --to=nils.faerber@kernelconcepts.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.