Subscribe to News

From TechnologicalWiki

Contents 1 GPLv2 1.1 GPLv2 & GPLv3 1.2 GPLv2 & LGPLv2 1.3 GPLv2 & LGPLv3 1.4 GPLv2 & EPL 1.5 GPLv2 & Apachev2 1.6 GPLv2 & EUPL 2 GPLv3 2.1 GPLv3 & GPLv2 2.2 GPLv3 & LGPLv2 2.3 GPLv3 & LGPLv3 2.4 GPLv3 & EPL 2.5 GPLv3 & Apachev2 2.6 GPLv3 & EUPL 3 LGPLv2 3.1 LGPLv2 & GPLv2 3.2 LGPLv2 & GPLv3 3.3 LGPLv2 & LGPLv3 3.4 LGPLv2 & EPL 3.5 LGPLv2 & Apachev2 3.6 LGPLv2 & EUPL 4 EPL 4.1 EPL & GPLv2 4.2 EPL & GPLv3 4.3 EPL & LGPLv2 4.4 EPL & LGPLv3 4.5 EPL & Apachev2 4.6 EPL & EUPL 5 Apachev2 5.1 Apachev2 & GPLv2 5.2 Apachev2 & GPLv3 5.3 Apachev2 & LGPLv2 5.4 Apachev2 & LGPLv3 5.5 Apachev2 & EPL 5.6 Apachev2 & EUPL 6 EUPL 6.1 EUPL & GPLv2 6.2 EUPL & GPLv3 6.3 EUPL & LGPLv2 6.4 EUPL & LGPLv3 6.5 EUPL & EPL 6.6 EUPL & Apachev2

GPLv2

[edit] GPLv2 & GPLv3

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

GPLv3 is not compatible with GPLv2 by itself. However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well. When this is the case, you can use the code under GPLv3 to make the desired combination.

[edit] GPLv2 & LGPLv2

If you consider to modify or link a code released under LGPLv2 and include it on you project that will be released under GPLv2, 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] GPLv2 & LGPLv3

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

However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well and 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.

It is not possible to dynamically link a LGPLv3 code with a project released under GPLv2.

[edit] GPLv2 & EPL

If you consider to modify a code released under EPL and include it on you project that will be released under GPLv2, 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 dynamically link a code released under EPL with the code from you project that will be released under GPLv2, 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] GPLv2 & Apachev2

If you consider to modify a code released under Apachev2 and include it on you project that will be released under GPLv2, 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 dynamically link a code released under Apachev2 with the code from you project that will be released under GPLv2, you should know that those licenses are NOT COMPATIBLE.

However if you have the ability to release the project under GPLv2 or any later version, you can choose to release it under GPLv3 or any later version—and once you do that, you'll be able to dynamically link the Apachev2 code. Apachev2 software can be included in GPLv3 projects, because the GPLv3 license accepts Apachev2 software into GPLv3 works.

[edit] GPLv2 & EUPL

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

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

If you consider to dynamically link a code released under EUPL with the code from you project that will be released under GPLv2, you should know that those licenses are NOT COMPATIBLE.

[edit] GPLv3

[edit] GPLv3 & GPLv2

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

If you have the ability to release the project under GPLv2 or any later version, you can choose to release it under GPLv3 or any later version—and once you do that, you'll be able to incorporate the code released under GPLv3.

[edit] GPLv3 & LGPLv2

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

If you want to modify the code first you should upgrade the LGPLv2 license to GPLv3. 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] GPLv3 & LGPLv3

If you consider to modify or link a code released under LGPLv3 and include it on you project that will be released under GPLv3, 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.

[edit] GPLv3 & EPL

If you consider to modify a code released under EPL and include it on you project that will be released under GPLv3, 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 and include it on you project that will be released under GPLv3, 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] GPLv3 & Apachev2

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

Apache 2 software can be included in GPLv3 projects, because the GPLv3 license accepts Apache 2 software into GPLv3 works.

[edit] GPLv3 & EUPL

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

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"

GPLv3 is not on the list of "compatible license" however dinamically link is not consider a substantinally combination so for dinamically link the licenses are COMPATIBLE.

[edit] 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

[edit] EPL

[edit] EPL & 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 EPL, you should know that those licenses are NOT COMPATIBLE.

GPLv2 and GPLv3 only permits that modification to its code are covered by the same license.

[edit] EPL & 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 EPL, you should know that those licenses are NOT COMPATIBLE.

GPLv2 and GPLv3 only permits that modification to its code are covered by the same license.

[edit] EPL & LGPLv2

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

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

[edit] EPL & LGPLv3

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

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

[edit] EPL & Apachev2

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

[edit] EPL & 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 EPL, you should know that those licenses are COMPATIBLE.

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

[edit] Apachev2

[edit] Apachev2 & 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 Apachev2, you should know that those licenses are NOT COMPATIBLE.

GPLv2 and GPLv3 only permits that modification to its code are covered by the same license

[edit] Apachev2 & 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 Apachev2, you should know that those licenses are NOT COMPATIBLE.

GPLv2 and GPLv3 only permits that modification to its code are covered by the same license

[edit] Apachev2 & LGPLv2

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

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

[edit] Apachev2 & LGPLv3

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

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

[edit] Apachev2 & EPL

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

They have incompatibilities with patents treatment If you consider to dinamically link a code released under EPL with you project that will be released under Apachev2, 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] Apachev2 & 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 Apachev2, you should know that those licenses are NOT COMPATIBLE.

Software under several F/OSS licences can be combined with EUPL software. It is the case with all components that are licensed under licences that do not impose restrictions on future licensing (all the “permissive licences").

[edit] EUPL

[edit] EUPL & 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 EUPL, you should know that those licenses are NOT COMPATIBLE.

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

[edit] EUPL & 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 EUPL, you should know that those licenses are NOT COMPATIBLE.

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

[edit] EUPL & LGPLv2

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

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

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

[edit] EUPL & LGPLv3

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

EUPL has a copyleft comparable to the GPL's. However, it allows recipients to distribute the work under the terms of other selected licenses, and some of those—the Mozilla Public License and the Common Public License in particular—only provide a weaker copyleft. Thus, developers can't rely on this license to provide a strong copyleft. The EUPL is incompatible with GPLv3, because recipients are not given permission to use GPLv3's terms, and the EUPL's copyleft conflicts with GPLv3's.

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

[edit] EUPL & EPL

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

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 EUPL, 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] EUPL & Apachev2

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

Software under several F/OSS licences can be combined with EUPL software. It is the case with all components that are licensed under licences that do not impose restrictions on future licensing (all the “permissive licences").

GPLv2 compatibility 
GPLv3 compatibility 
LGPLv2 compatibility 
EPL compatibility 
EUPL compatibility