Hacker News new | ask | show | jobs
by critic 6293 days ago
By accompanying your object code with GPL/LGPL, you are promising your customers that your code is GPL/LGPL, i.e. you will be bound to open your code.

The fact that your understanding of the license is different shows just how sneaky and obfuscated LGPL is.

1 comments

If that were true, why would would the FSF say that "using the Lesser GPL permits use of the library in proprietary programs; using the ordinary GPL for a library makes it available only for free programs" [http://www.gnu.org/licenses/why-not-lgpl.html]? The LGPL is not designed to trick you into using the moral equivalent of the GPL; it's designed to occupy the middle ground between GPL and BSD licenses.
Nonsense.

> Lesser GPL permits use of the library in proprietary programs

That means "in some cases", not "in all cases". Logical fallacy on your part.

> ordinary GPL for a library makes it available only for free programs

Here, GPL'ers contradict themselves (for both senses of "free"). GPL code can, technically, be non-gratis. And GPL code can be used in non-GPL programs (you just can't distribute them easily).