-
Notifications
You must be signed in to change notification settings - Fork 76
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
Supporting unrar introduces licensing issues #565
Comments
This was referenced Dec 3, 2023
yo I think we forgot to close this one! |
Yeah, I suppose we can consider this completed. The ideal solution would of course be to switch to a FOSS unrar library, but until such demand arises and someone volunteers to work on it, I think this is good enough for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The underlying C++ library of unrar.rs uses a proprietary license that includes some hostile restrictions. As explained by Fedora Wiki, these restrictions make it GPL-incompatible and non-free.
ouch
does not distribute unrar sources directly, which means it's not subjected to the requirements of term 2, which means it can continue to be licensed under MIT license (I think; obligatory "not a lawyer").ouch
would still require non-free code, which makes it legally impossible to include it in FOSS-only distributions like Debian and Fedora, or to build it using third-party build services with FOSS-only TOS (namely Fedora COPR).As I see it, there are two ways to solve this problem:
Of course, the two are not mutually exclusive. I will submit a PR for the feature-gate first.
The text was updated successfully, but these errors were encountered: