3 ms·
Building an application executable may or may not violate the LGPL. It likely depends on whether the application allows new versions of the LGPL-covered modules
by kazinator 8y ago
Building an application executable may or may not violate the LGPL. It likely depends on whether the application allows new versions of the LGPL-covered modules to be loaded into it. The simple question is: can users exercise their LGPL-granted rights to that library: to modify the library code, and still use it with the proprietary application?
(FWIW, I've written a Lisp implementation that has compile-file and load, similar to Common Lisp.)
A Lisp-ified LGPL might seem perfect, but on the other hand there are some good reasons not to introduce derivative versions of de facto standard licenses.
- _ph_ 8y agoThat is, why Franz wrote the LLGPL as a preamble to the LGPL. So the LGPL text is copied, only clarified in the Lisp context by the preamble.