|
Rockbox mail archiveSubject: Re: [Theme Editor] Weekly Status Report #7Re: [Theme Editor] Weekly Status Report #7
From: Thomas Martitz <thomas.martitz_at_student.htw-berlin.de>
Date: Sun, 04 Jul 2010 15:30:41 +0200 Am 04.07.2010 14:58, schrieb Rafaël Carré: > - If we want to*link* to a LGPLv3 library, no problem (as even > proprietary code can link to LGPLv3) > - If we want to*copy* LGPLv3 code and statically link it in a > binary made with our "GPLv2 or later" code, we must "upgrade to > GPLv3" > I understood it this way: Every file that's distributed under 'GPLv2 or later' terms can be used under the terms of GPLv3 (due to the 'or later' bit) and is hence implicitly dual licensed. I.e. you can copy and statically link these files into GPLv3 projects. What would be the point of the 'or later' if you couldn't use it in v3 projects anyway? It would be equivalent to GPLv2 only, no? Also, this has probably been discussed at the 2008 devcon in Berlin. Best regards. Received on 2010-07-04 Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy |