Apache License v2.0 compat question

[grorp]

Apache License v2.0 + GPL v2 seems to be a problem: https://www.gnu.org/licenses/license-list.en.html#apache2
Does this apply to LGPL v2.1 too and is it a problem here / does it apply to our situation?
~ grorp

No idea. We already use Apache 2.0 assets - refresh, Arimo and Digit
~ rubenwardy

Might be worth making an issue for this?
~ rubenwardy

Originally posted in #15254 (comment)

[sfence]

See: https://www.apache.org/legal/resolved.html#category-x
At least, you can not add LGPL 2.1 code to Apache 2.0 code.

But it looks to be possible to add Apache 2.0 licensed code into GPLv3 licensed project. In that case, the author probably only has to follow some Apache 2.0 rules which are not necessary for GPLv3 code. https://www.apache.org/licenses/GPL-compatibility.html

So if it is LGPLv2 or later, it can be upgraded to LGPLv3 and everything should be fine for sure.

It looks like adding Apache 2.0 code into LGPL 2.1 project as a separate file should be also fine. Looks like Apache 2.0 is more strict in some points, but not in conflict with LGPL 2.1 requirements.

[sfence]

Looks like this is needed to be applied to Apache 2.0 to be compatible with GPL v2 -> https://spdx.org/licenses/LLVM-exception.html

By my understanding, if the license is ok with GPL v2, it is ok with LGPL v2 and similar for GPL and LGPL v3. (because LGPL are the same as GPL, only with added linking exception/permission).

[sfan5]

Does this even apply? It's media files and not code we link, load or include.