On Mon, 4 Oct 1999, Bradley D. LaRonde wrote:
> So why not use LGPL? IOW, why use MPL instead of LGPL?
It's both less restrictive and designed to apply to anything; not just a
library with a well defined interface API. It's also more sensibly
designed (try reading them both and comparing them side by side- I did),
and has passed a review by qualified solicitors (at Netscape). The FSF
really seem to have the opinion that all code should be available under
the GPL or not at all, and the LGPL is intentionally awkward to apply to
anything other than a straight "link it in and it provides these
functions" library to encourage people not to use it for anything else.
The MPL is a much more elegant solution to the problem where you want to
be able to link proprietory code to free code, and keep the free code free
(and contribute improvements to it back) without having to release the
proprietory code under the same license.
--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------
