
2010/7/21 Ketil Malde
John Goerzen
writes: I need to read the LGPL and analyze it closer, but my first analysis suggests that this would work fine for me and others.
I'm using the LGPL for library code, and GPL for applications. Although a lot of noise is generated from the linking issues, the most imporant point to me is that LGPL allows you to use the library in other open source (but non-GPL-compliant) applications.
Binary/commercial/proprietary software - well, I'll worry about it the day it happens. So far, nobody ever asked for a BSD license - but I'd be happy about an exception (even with modifications to the library, as long as those modifications were available).
For a LGPL library, why do you make the distinction between open source and proprietary applications? They can all link to a LGPL library. Cheers, Thu