From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] libsensors license question - GPL or LGPL ?
Date: Thu, 27 Nov 2014 17:32:42 +0000 [thread overview]
Message-ID: <5477603A.70105@roeck-us.net> (raw)
In-Reply-To: <54762A5A.7030601@roeck-us.net>
Hi Jean,
On 11/27/2014 02:24 AM, Jean Delvare wrote:
> Hi Guenter,
>
> On Wed, 26 Nov 2014 11:30:34 -0800, Guenter Roeck wrote:
>> libsensors is supposed to be licensed under LGPL as far as I can see
>> and recall. However, doc/developers/applications reads:
>>
>> Note that libsensors falls under the GPL, not the LGPL.
>> In more human language, that means it is FORBIDDEN to link any application
>> to the library, even to the shared version, if the application itself
>> does not fall under the GPL. This may or may not be changed in the future.
>> Contact us if you wish to discuss your application.
>>
>> Is that an oversight from earlier versions or on purpose ?
>> The source refers to LGPL as far as I can see, and the comment in
>> lib/libsensors.3 states that it is distributed under LGPL.
>
> This is an horrible oversight. libsensors was originally under GPL,
> but I changed the license to LGPL with the approval of all authors and
> copyright holders:
> http://www.lm-sensors.org/wiki/LibsensorsLicense
>
> So starting with version 3.2.0, the only license for libsensors is LGPL.
>
> I'll fix the documentation immediately, thanks for pointing out my
> mistake.
>
No problem, thanks for the clarification.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2014-11-27 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 19:30 [lm-sensors] libsensors license question - GPL or LGPL ? Guenter Roeck
2014-11-27 10:24 ` Jean Delvare
2014-11-27 17:32 ` Guenter Roeck [this message]
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=5477603A.70105@roeck-us.net \
--to=linux@roeck-us.net \
--cc=lm-sensors@vger.kernel.org \
/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.