> My vote: the ezFCPlib dir under fcptools be LGPL. Too late - they are GPL
If a commercial developer wishes to use ezFCPlib, they're welcome to apply to me for a license (which I can issue, since as the author I am exempt from the GPL). Offers above $1,000,000 considered. David ----- Original Message ----- From: "Jay Oliveri" <[EMAIL PROTECTED]> To: "David McNab" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, October 11, 2001 6:30 PM Subject: Re: License of ezFCPlib > On Wednesday 10 October 2001 03:04 am, [EMAIL PROTECTED] wrote: > > Zitiere David McNab <[EMAIL PROTECTED]>: > > > > if you turn ezFCPlib > > > > into GPL every program that is linked against it > > > > has to be released under GPL, too. (thinking of > > > > programs that are closed source at the moment) > > > > LGPL does avoid that problem. > > > > > > Problem? What problem? > > Basically, releasing a library under the GPL means no one can make > their own freenet client and use the library unless it's also released > under a GPL compatible license. > > It's common to release libraries (like libezfcp.a) under the LGPL so > that commercial applications can make use of the library as well. > > The rest of the tools (freeweb as well) should remain pure GPL as they > already are. > > My vote: the ezFCPlib dir under fcptools be LGPL. > > -- > Jay Oliveri "In the land of the blind, > GnuPG ID: 0x5AA5DD54 the one-eyed man is king." > _______________________________________________ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
