3 ms·
There's both a COPYING file that has the GPLv3 in it, and a COPYING.LESSER file with the LGPL in it. I can't tell what's meant by that. Dual licensed? Or port
by tyingq 6y ago
There's both a COPYING file that has the GPLv3 in it, and a COPYING.LESSER file with the LGPL in it. I can't tell what's meant by that. Dual licensed? Or portions GPLv3 and portions LGPL?
- e12e 6y agoLook at the actual files for copyright (or copyleft, if you will): http://git.savannah.gnu.org/cgit/lightning.git/tree/lib/lightning.c http://git.savannah.gnu.org/cgit/lightning.git/tree/lib/ligh... Looks like the libraryis lgpl,I couldn't find licensefor the docs themselves (I assume they use document license (COPYING.DOC)). There seemsto be at least one example program that is gpl: http://git.savannah.gnu.org/cgit/lightning.git/tree/doc/body.texi#n1671 http://git.savannah.gnu.org/cgit/lightning.git/tree/doc/body...
- elvis70 6y agoIt's under LGPL. The LGPL allows you to relicense your work under the GPL, if you want.
- bonzini 6y agoThe LGPLv3 is implemented as a set of additional permission on top of the GPLv3. The library is LGPL.
- segfaultbuserr 6y agoSince GPLv3, {L,}GPL have been "grand unified" to simplify things. Like code reuse, LGPLv3 is a just small patch on top of GPLv3 that says "given Condition X, you don't have to follow Clause Y in GPLv3", it's literally just a few short paragraphs. Without the original GPLv3 text, LGPLv3 is meaningless, like a running an executable without its shared library. Hence, although many people don't realize it, technically every project that licenses itself under LGPLv3 must contain a copy of GPLv3.