linux-kernel - Re: GPLv3 dispute solution

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0706181541050.14890@asgard.lang.hm>
Date:	Mon, 18 Jun 2007 15:43:02 -0700 (PDT)
From:	david@...g.hm
To:	Joshua David Williams <yurimxpxman.lkml@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: GPLv3 dispute solution - new open source license?

On Mon, 18 Jun 2007, Joshua David Williams wrote:

> On 6/18/07, Carlo Wood <carlo@...noe.com> wrote:
>
>>  Now, writing yet another license for the linux kernel is
>>  therefore NOT the solution - if you get my drift.
>
> The new license could be written to be compatible with both versions of the
> GPL. IMO, a new license written from the OSS perspective would behoove us
> greatly in that we are no longer subject to this Higher Calling of the FSF
> and the Church of Emacs.

no it couldn't

the GPLv2 says that if you combine it with any other license the result 
must be GPLv2

the GPLv3 says that if you combine it with any other license the result 
must be GPLv3

so you have one requirement saying that the result must be GPLv2 and 
another that says you must be GPLv3. there isn't any way to resolve this 
conflict.

David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/