On 29/05/12 12:31, Henri Sivonen wrote: >> There are several reasons; one of them is that companies wish to combine >> our stuff with proprietary code (a usage model which Mozilla has always >> enabled). This is harder with the LGPL because of the wider scope of its >> copyleft. > > How realistic will it be to combine first-party Mozilla code with > proprietary code in an LGPL-incompatible way once Mozilla first-party > code becomes dependent on LGPLed third-party code?
It depends what you mean by "in an LGPL-incompatible way". Assuming we keep the LGPLed code in its own shared library, then the person doing the combining will need to obey the terms of the relevant version of the LGPL (e.g. making source available and, for LGPLv3 allowing the library to be replaced etc.) for that code. If the way they supply code to their customers doesn't comply with this, they would need to change their practices/licence. Just as they might do on the upgrade from MPL 1.1 to MPL 2, which has slightly different (and easier to comply with) terms. Gerv _______________________________________________ legal mailing list [email protected] https://lists.mozilla.org/listinfo/legal
