Frank, I don't know, if I misunderstood you (late here), so please
excuse possible misunderstandings.
Frank Hecker wrote:
[MPL incompatible with GPL -> MPL incompatible with LGPL]
> I do not see how it could be compatible with the LGPL; what is
> different about the LGPL and the GPL in this regard?
What is different about GPL and LGPL is that the LGPL allows linking
with non-(L)GPL code. So, if the Mozilla code is kwpt in a lib, it can
be used together with another LGPL library and the executable could
still be under an (almost) arbitary license. At least, that is my
understanding. Not sure, if that is still the case, if the LGPL code
(lib or main code) uses non-GPL code.
This are different, if you want to mix ccode parts, not just the whole libs.
> Because using it (really, distributing it) under MPL terms wouldn't
> allow it to be included in an LGPLed library distributed under LGPL
> terms, _if_ you agree that the MPL is "incompatible" with the LGPL.
> (See above.)
In most cases (e.g. embedding Gecko), you'd use Mozilla code as complete
lib, I think. So, you might be fine.
Still, reusing Mozilla code directly (as snipplets) in LGPL projects is
IMO desirale. Especially, if we get it that cheap.
P.S. shoundn't we remove .general from disitribution now?
