At 09:45 16/03/2001 +0100, Martin Kutschker wrote:
>Hi!
>
>The subject says, what I want to do. In particular it's an ("open source")
>arbitrary precision lib. There are several of the libs available, some of
>them are GPLd others are LGPLd.
In general it goes like this. The MPL and NPL are file based licences so
they can interface with any other licence on a file boundary. LGPL is
similar, and there is no harm in connecting MPL and LGPL code in that
way. The LGPL code wouldn't make it into the tree though.
For GPL code the problem is with GPL, neither MPL nor NPL restrict you in
connecting to any other licence, GPL however does restrict you from using
GPL licenced code with just about any other licence without specific
permission from the original copyright holder (actually some might disagree
with the word original there given GPL's ability to deny copyright).
If you use a dual-licence for your own code MPL/GPL then some will say that
that is sufficient to meet the GPL requirements of the existing code you
want to use. However, it would not be possible to contribute that code
back to Mozilla because you aren't able to relicence the original GPL code
under the MPL.
The answer is to persuade the owners of the code you want to use to also
licence their code under the MPL or equivalent licence. This of course
blows away the whole argument for a dual licence of Mozilla but that's an
entirely different point and not one that affects this case.
To summarise, you can interface your own code to GPL code and use that with
Mozilla so long as you also licence your code as MPL and make it clear that
you do so. You will not be able to contribute that code back to Mozilla
though if it depends on GPL'd only code.
As in all this its much the best course to take legal advice and follow that.
Simon
>I don't care too much about the licening of my own code. If possible I would
>like contribute it to the Mozilla project (similar to the JS I/O
>extensions).
>
>Further I want to use the XPCOM object in a XUL application.
>
>May I use a GPLd lib? If this means the wrapper is also GPLd, that's fine
>with me. It's ok for the app as well. But - is it ok to write a GPLd XUL app
>for Mozilla?
>
>As for the LGPLd libs, is it true that I may use them as long as I
>distribute the libs source with my wrapper/app?
>
>Thanx for helping a confused
> Masi
===================================================
If I'd known I would spend so much time sorting and rearranging boxes
I'd have paid more attention at kindergarten
S.P. Lucy
