While IANAL, my understanding of the situation is that LGPL was designed
exactly for such a situation.
The deciding point is whether your customer can customize your application
by modifying the LGPLed library and using his modified executable with
your application; and whether he can share his modifications with the rest
of the world. All the rest are technicalities.
For example, the customization could be due to having to fix a bug, which
reached your customer's attention but you are too lazy to fix.
--- Omer
WARNING TO SPAMMERS: see at http://www.zak.co.il/spamwarning.html
On Wed, 18 Oct 2000, Felix Shvaiger wrote:
> Hi All !
>
> May I develop proprietary application (executable) that uses LGPLed library
> in form of shared library and distribute nothing but:
> 1. executable file itself
> 2. my proprietary license for this executable
> 3. notice that this executable uses some LGPLed libraries
> 4. shared object file of LGPLed library (to make my executable working)
> 5. LGPL license file
> 6. link do LGPLed library's source code download site
> 7. instructions about making shared library from source
>
> Have I got it right ?
>
> Do not ask, why I don't GPL my applications - it is not up to me.
>
> Excuse me if it is "off topic".
=================================================================
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]
