Comment by CJefferson
9 years ago
Except, I work on GPL v2 systems, and we can't link to GPL v3 libraries. No other license I've worked with has this incompatiblity problem.
9 years ago
Except, I work on GPL v2 systems, and we can't link to GPL v3 libraries. No other license I've worked with has this incompatiblity problem.
> Except, I work on GPL v2 systems, and we can't link to GPL v3 libraries.
The standard way to use GPL v2 is to use this verbiage:
If someone doesn't do that, I don't know what to say.
That's the wrong direction. You can use v2 code with that sentence in the license in a v3 codebase, not vice-versa (unless you upgrade your codebase to v3 entirely, but since GPLv2 was explicitly mentioned that probably is not an option for whatever reason).
At some point in the far distant past, someone decided they didn't want to give the FSF the ability to apply any license they like to their software (which is reasonable, the FSF could in principle make GPL v4 -- All your source are belong to us).
While that choice might have been a mistake, it would now be an impossible effort to get all contributor's permission to change, so we are stuck with v2.