LGPLv2 compatibility

From TechnologicalWiki

LGPLv2

[edit] LGPLv2 & GPLv2

If you consider to modify or dinamically link a code released under GPLv2 and include it on you project that will be released under LGPLv2, you should know that those licenses are COMPATIBLE.

LGPLv2.1 gives you permission to relicense the code under any version of the GPL since GPLv2. If you can switch the LGPLed code in this case to using an appropriate version of the GPL instead (GPLv2), you can make this combination.

[edit] LGPLv2 & GPLv3

If you consider to modify or dinamically link a code released under GPLv3 and include it on you project that will be released under LGPLv2, you should know that those licenses are COMPATIBLE.

LGPLv2.1 gives you permission to relicense the code under any version of the GPL since GPLv2. If you can switch the LGPLed code in this case to using an appropriate version of the GPL instead (GPLv3), you can make this combination.

[edit] LGPLv2 & LGPLv3

If you consider to modify or dinamically link a code released under LGPLv3 and include it on you project that will be released under LGPLv2, you should know that those licenses are COMPATIBLE.

LGPLv3 gives you permission to relicense the code under GPLv3. In these cases, you can combine the code if you convert the LGPLed code to GPLv3 and LGPLv2.1 gives you permission to relicense the code under any version of the GPL since GPLv2. If you can switch the LGPLed code in this case to using an appropriate version of the GPL instead (GPLv3), you can make this combination.

[edit] LGPLv2 & EPL

If you consider to modify a code released under EPL and include it on you project that will be released under LGPLv2, you should know that those licenses are NOT COMPATIBLE.

EPL's weak copyleft and choice of law clause make it incompatible with the GNU GPL. EPL removes the broader patent retaliation language regarding patent infringement suits specifically against Contributors to the EPL'd program.

Only the owner of software can decide whether and how to license it to others. Contributors to a Program licensed under the EPL understand that source code for the Program will be made available under the terms of the EPL. Unless you are the owner of the software or have received permission from the owner, you are not authorized to apply the terms of another license to the Program by including it in a program licensed under another Open Source license.

If you consider to dinamically link a code released under EPL with you project that will be released under LGPLv2, you should know that those licenses are COMPATIBLE.

The Eclipse Foundation interprets the term "derivative work" in a way that is consistent with the definition in the U.S. Copyright Act, as applicable to computer software. Therefore, linking to Eclipse code might or might not create a derivative work, depending on all of the other facts and circumstances.

[edit] LGPLv2 & Apachev2

If you consider to modify a code released under EPL and include it on you project that will be released under LGPLv2, you should know that those licenses are NOT COMPATIBLE.

Apache v2 include certain patent termination and indemnification provisions that are not considered under GPLv2 and LGPLv2.

If you consider to dinacally link a code under Apachev2 with your project that will be released under LGPLv2, you should first Upgrade the LGPLv2.1 code to LGPLv3 to make the licenses COMPATIBLE.

Apache v2 include certain patent termination and indemnification provisions that are not considered under GPLv2 and LGPLv2. However LGPLv2.1 gives you permission to relicense the code under any version of the GPL since GPLv2. If you can switch the LGPLed code in GPLv3, you can make this combination as Apache 2 software can be included in GPLv3 projects, because the GPLv3 license accepts Apache 2 software into GPLv3 works.

[edit] LGPLv2 & EUPL

If you consider to modify or dinamically link a code released under EUPL and include it on you project that will be released under LGPLv2, you should know that those licenses are COMPATIBLE if you upgrade the code to GPLv2.

LGPLv2.1 gives you permission to relicense the code under any version of the GPL since GPLv2. If you can switch the LGPLed code in this case to using an appropriate version of the GPL instead (as noted in the table), you can make this combination. If you substantially combine EUPL software with software distributed under a "compatible licence", the EUPL allows the resulting software to be distributed under the compatible licence instead of distributing it under the EUPL itself. The compatible licences are currently defined by the EUPL as being the:

• GNU General Public licence (GNU GPL v.2)
• Open Software licence (OSL) v. 2.1, v. 3.0
• Common Public licence v. 1.0
• Eclipse Public licence v. 1.0
• CeCILL v. 2.0