Licenses...

[Robin Becker]

In article <37AE9B42.4DF40758 at lemburg.com>, M.-A. Lemburg
<mal at lemburg.com> writes
...
>If you link against a GPLed product (even if it's done dynamically!),
>the whole construction (your product + the GPLed one) automatically
>fall under the GPL. This means that you can still sell and distribute
>your product, but only if you include the full source code of
>the GPLed product
>*plus* your product.
>
Oh dear; I wrote this extension called dll for Tcl that allows tcl code
to link to arbitrary dll's. The source code for the extension is
available. Must I distribute source for all known GPL'd products which
can be linked to tcl using this extension. As it happens this thing is
mostly used by win32ers, but it has run under Linux.
>The LGPL is a little different: it allows you to link against the
>LGPLed product without the need to ship your source code. You still
>have to include the source code of the LGPLed product you're linking
>against though (including any changes that you have made to it).
>
>If you are using Python extensions written by different authors,
>be sure to check their license statement. In case you have any
>doubts get in touch with them before using their code. Most 
>extensions are under very similar licenses as Python itself,
>but some a GPLed and other LGPLed. Also, some are not valid for
>commercial use meaning that you'll have to negotiate a special
>license with the author to be able to use in your code. This
>usually involves paying a license fee.
>
>Hope this clarifies things a little. More infos on GPL and LGPL
>should be available on www.gnu.org. If you are still unsure what
>is legal and was is not, go on the safe side and contact your
>lawyer to get things straight.
>

-- 
Robin Becker