Re:Copyleft and community licenses are not without merit, bu...
by SpicyLemonZest on Friday December 21, 2018 @10:22PM
(#18738721)
The LGPL works as you're describing; I can license my own code however I want, as long as I let people freely modify all the LGPL libraries it links in. The GPL proper is very deliberately viral.
[ Parent
| on HN ]
Re:Copyleft and community licenses are not without merit, bu...
by robocat on Friday December 21, 2018 @10:58PM
(#18738827)
The LGPL is fine for libraries - but that limits where it can be used.
I think the LGPL becomes something just like the GPL for scripting languages because there is no "linking" for many languages.
For example an npm package for nodejs can't be made into a "library" - all the source is "compiled" together at runtime.
Re:Copyleft and community licenses are not without merit, bu...
by cyphar on Saturday December 22, 2018 @01:26AM
(#18739294)
If you can replace an LGPL component with a changed version then you don't need to license any additional code under the LGPL. Shared libraries are just one mechanism for doing this.