News for hackers. Stuff that matters.
Re:The GNU Manifesto Turns Thirty by lazaroclapp on Tuesday March 17, 2015 @02:09PM (#9219985)
Isn't this sort of scenario the reason the LGPL exists? That way one can use the library in proprietary projects if needed, but any modifications to the library itself must still be open sourced, under the same license.
Re:The GNU Manifesto Turns Thirty by oddevan on Tuesday March 17, 2015 @03:20PM (#9220556)
The LGPL also imposes restrictions on the finished product, including (but not limited to) requiring the right to reverse-engineer the product so that a modified library can be incorporated.
Re:The GNU Manifesto Turns Thirty by davexunit on Tuesday March 17, 2015 @03:59PM (#9220914)
>the right to reverse-engineer the product

Doesn't sound like a restriction to me.

Re:The GNU Manifesto Turns Thirty by JetSpiegel on Tuesday March 17, 2015 @04:49PM (#9221339)
I think it's an anti-tivoisation clause.
Re:The GNU Manifesto Turns Thirty by davidw on Tuesday March 17, 2015 @02:17PM (#9220049)
Yes, but it was by way of example: sometimes it's not quite so clear cut.
Re:The GNU Manifesto Turns Thirty by lazaroclapp on Tuesday March 17, 2015 @06:09PM (#9221937)
Fair enough. Just pointing out there are three options:

- Let people do whatever they want with it (BSD).

- Let people use it as a library, but force them to release changes to the library itself (LGPL).

- Let people use the software, but force them to release all modifications (GPL).

Neither is good or bad, but depends on the intention of the developer. Also, as a matter of etiquette, contributing changes back even for BSD code should be the norm, whenever there is no reason not to do so. But (L)GPL puts some enforcement power behind that rule of etiquette (and arguably created the norm).