Re: LGPL v3 compatibilty (original) (raw)
- To: debian-legal@lists.debian.org
- Subject: Re: LGPL v3 compatibilty
- From: Walter Landry <walter@geodynamics.org>
- Date: Mon, 16 Jul 2007 00:15:37 -0700 (PDT)
- Message-id: <[🔎] 20070716.001537.108738754.walter@geodynamics.org>
- In-reply-to: <[🔎] 20070715085749.44a0e41c.frx@firenze.linux.it>
- References: <[🔎] 20070702195203.230b2604.frx@firenze.linux.it> <[🔎] 20070714.215627.59466330.walter@geodynamics.org> <[🔎] 20070715085749.44a0e41c.frx@firenze.linux.it>
Francesco Poli frx@firenze.linux.it wrote:
On Sat, 14 Jul 2007 21:56:27 -0700 (PDT) Walter Landry wrote:
Francesco Poli frx@firenze.linux.it wrote:
On Mon, 2 Jul 2007 12:31:13 -0400 Anthony Towns wrote:
[...]
Note that if we do stick to the view we've taken up until now, when we have a LGPLv3 only glibc in the archive, we'll no longer be able to distribute GPLv2-only compiled executables.
Unless the GPLv2-only work copyright holder(s) add(s) a special exception, similar to the one needed to link with the OpenSSL library, right?
This scenario is worrying me... :-(
Is this going to be a problem for the kernel? It is definitely not going to go to GPLv3.
Is the Linux kernel linked with any LGPL'd work? AFAIUI, it is not, so no problem for the kernel.
Doesn't the kernel get its implementations for pow(), sqrt(), printf(), and the rest of the C standard library from glibc, which is LGPL'd?
Cheers, Walter Landry walter@geodynamics.org
Reply to:
- Follow-Ups:
- Re: LGPL v3 compatibilty
* From: Måns Rullgård mans@mansr.com
- Re: LGPL v3 compatibilty
- References:
- Re: LGPL v3 compatibilty
* From: Francesco Poli frx@firenze.linux.it - Re: LGPL v3 compatibilty
* From: Walter Landry wlandry@ucsd.edu - Re: LGPL v3 compatibilty
* From: Francesco Poli frx@firenze.linux.it
- Re: LGPL v3 compatibilty
- Prev by Date:Re: LGPL v3 compatibilty
- Next by Date:Re: LGPL v3 compatibilty
- Previous by thread:Re: LGPL v3 compatibilty
- Next by thread:Re: LGPL v3 compatibilty
- Index(es):