NYCPHP Meetup

[Tim Gales]

Brian Kaney writes:
> As I understand it, typically extensions and libraries are released
> under the LGPL.  This allows people use the extension in some larger
> application without binding it (i.e. the application could be released
> under any license).  However, if changes are made to the specific
> library, the modifications would also fall under the LGPL.
> 

Thanks for you response.

In the case that I am considering, I would 
take something which is already GPL and 
sort of turn it into a library.

It seems (I think) I would not be allowed to 
turn GPL code into LGPL just by making 
it into a library.

I am starting to think I should just 
write the whole thing from scratch 
and license it however the client wants -- 
seems a shame though.

T. Gales & Associates
'Helping People Connect with Technology'

http://www.tgaconnect.com