GPL? Shouldn't it have been LGPL?

Topics: Developer Forum
Nov 3, 2007 at 11:25 AM
Typically, libraries are LGPL, which means that you can use it everywhere, but if I make changes, I should share them with all.

GPL a library like ExcelPackage means that every program that uses it must be GPL, which will reduce the use of ExcelPackage drastically, since most Excel-applications used by companies.

Anyone know of an alternative to ExcelPackage that isn't GPL?
Jan 6, 2008 at 11:41 AM
LGPL would be great indeed.
(or other license that lets me include this library in a closed source (commercial) application)
Feb 20, 2008 at 2:47 AM
I agree that LGPL would have been great in order to be able to use this library in a commercial app. Any feedback on this?
Jan 20, 2009 at 9:32 PM
This library is exactly what I need, but because I am writing proprietary software I simply cannot use it.  What a bummer!
I'm guessing that the GPL was chosen over the LGPL for reasons outlined here:  Why you shouldn't use the Lesser GPL for your next library