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
libgpiod cxx bindings license LGPLv3+ #772
Comments
Which part of |
In general I think the LICENSE field in yocto recipes is what SPDX calls a license expression:
My concrete understanding of the semantics of the LICENSE field in libgpiod is:
The libgpiod C++ bindings are now re-licensed LGPL-3.0-or-later, that means a user of the library does not have the choice to use those under LGPL-2.1 anymore -- and imho the package's LICENSE field should reflect that. This results in practice the LICENSE field cannot be used by yocto anymore to identify incompatible licenses or to generate concise SBOMs for the build artifacts. I think this could be solved the following way, setting the LICENSE for the libgpiodcxx subpackage setting to LGPL-3.0-or-later, something like this for libgpiod-2.1.bb
|
I see. Yes it makes sense but if you want to be 100% strict then there would be non LGPL-3.0 files too in the libgpiod package. Do you want to send a patch to the list? |
Sorry, I don't fully understand. Did you mean to say libgpiodcxx package?
Honestly I don't have much experience with sending patches and would prefer creating a PR here. But if that's usual openembedded development workflow, yes. |
Dear maintainers, @brgl,
I noticed that the the libgpiod cxx bindings have been re-licensed from LGPLv2+ to LGPLv3+ starting from version 2.0.
https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/commit/bindings/cxx/gpiod.hpp?id=ea84f882d5d39b734a5756b3a6950da4896b9a0a
I think this should be in reflected in the LICENSE line of
libgpiod_2.1.bb which currently lists only
The text was updated successfully, but these errors were encountered: