On Wed, 19 Jul 2000, Matti Picus wrote:

> But can't LGPL be used to build proprietary applications? Just build the 
> proprietary stuff as a library, supply only the main.c source along with 
> the libraries and headers, and you are OK, no?

you don't have to expose the source code of an application that uses
LPGL-ed libraries. unlike GPL, the LGPL license is not of a "poisenous"
nature. only if you make changes to the LGPL-ed library itself - you need
to redistribute those.

guy

"For world domination - press 1,
 or dial 0, and please hold, for the creator." -- nob o. dy


=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to