All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] prog/dump/util.c is GPL version 2 only licensed
Date: Wed, 15 Aug 2007 08:31:44 +0000	[thread overview]
Message-ID: <20070815103144.32e3f33d@hyperion.delvare> (raw)
In-Reply-To: <46C0C758.5060509@hhs.nl>

Hi Hans,

On Tue, 14 Aug 2007 22:52:32 +0200, Hans de Goede wrote:
> Jean Delvare wrote:
> > Now I realize that it probably doesn't make much sense to release just
> > one file with a different license, it hardly serves any practical
> > purpose and can only add to confusion. If it has any legal value at
> > all... So I am fine re-licensing that file if it makes you happy.
> 
> Yes, please relicense it.

Done.

>                           Most people don't realize it but once libraries GPL 
> v2 only code depends on become LGPL 3, then the GPL v2 only code can no longer 
> be distributed (atleast not as part of a distribution containing LGPL v3 
> versions of the libs the GPL v2 only code depends on).

I don't get it. You can link even closed-source code with
LGPLv2-licensed code (that was the purpose of this license over GPLv2).
Is this something that changed with LGPLv3? If not, how could you not
be allowed to link GPLv2 code then?

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-08-15  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 21:04 [lm-sensors] prog/dump/util.c is GPL version 2 only licensed Hans de Goede
2007-08-14 13:48 ` Jean Delvare
2007-08-14 20:52 ` Hans de Goede
2007-08-15  8:31 ` Jean Delvare [this message]
2007-08-15  9:06 ` Hans de Goede

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=20070815103144.32e3f33d@hyperion.delvare \
    --to=khali@linux-fr.org \
    --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.