You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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:
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!
The text was updated successfully, but these errors were encountered: