-
Notifications
You must be signed in to change notification settings - Fork 37
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
Cargo Deny complains about LGPL-3.0 licenses #1786
Comments
IANAL, but LGPL-3 section @stevenj Would this be an option in your case? i.e. as long as the application using |
Your right, but Apache2 allows distribution in Object form without source, it's not Copyleft. So the LGPL license prevents anyone from taking advantage of this aspect of the Apache 2 license. My current use case is in a library which is itself Apache2, so having a LGPL library restricts the scope of the Apache 2 license to that of LGPL (Source, or re-linkable against object files). It's not urgent, I raised this issue because I will, at some point in the near future, raise a PR to address this with a feature flag. Is there a performance or some other reason behind the library choice? Not trying to second guess it, just after more context because there is already a non LGPL alternative supported by the code? |
Context & versions
cargo deny check
complains that the mithril libraries rely onLGPL-3.0+
licensed dependencies.This is a problem for code because these libraries are statically linked, which means that any consumer can not produce a binary only version of the code. As the LGPL requires that the program must be able to be relinked.
Output of
cargo deny check
Steps to reproduce
Run
cargo deny check --exclude-dev
on the code.Actual behavior
Links against LGPL code without the option to select it.
Expected behavior
The libraries in-question have non LGPL counterparts already but there is no way to select them, its automatically chosen based on architecture.
It would be nice to expose a feature flag to control which library is used.
The text was updated successfully, but these errors were encountered: