Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License incompatibility with GPLv2 #2

Closed
Infernio opened this issue Jun 12, 2020 · 1 comment
Closed

License incompatibility with GPLv2 #2

Infernio opened this issue Jun 12, 2020 · 1 comment

Comments

@Infernio
Copy link

Hey Ganda :)

We'll eventually want Wrye Bash to either depend on this or to merge it into the Wrye Bash codebase. Unfortunately, the Apache 2.0 license used for pynxm currently makes this impossible since Wrye Bash uses the GPLv2:

Despite our best efforts, the FSF has never considered the Apache License to be compatible with GPL version 2, citing the patent termination and indemnification provisions as restrictions not present in the older GPL license. The Apache Software Foundation believes that you should always try to obey the constraints expressed by the copyright holder when redistributing their work.

So the best solution would be to either switch the license to something that's compatible with GPLv2 (MIT/BSD/LGPLv2.1/GPLv2) or to dual-license under one of those.

Granted, we've technically been violating libloot-python's license (GPLv3) for years by packaging it with a GPLv2 program - thankfully Ortham is highly unlikely to complain about that :P. Still, I don't exactly want to violate more licenses now.

Thanks!

@Infernio
Copy link
Author

Ref wrye-bash/wrye-bash#531 - turns out we don't really have to worry because we're GPLv2 or later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant