Change component identification license to SPDXIDs #998
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also added a new identification for systemd and openssh Signed-off-by: Jens Lucius <github@jenslucius.de>
|
Thank you for this great PR. Looks good, will do a testrun during the next days. |
Signed-off-by: Jens Lucius <github@jenslucius.de>
m-1-k-3
approved these changes
Jan 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Change the license identification of components in S09 to SPDX license short identifiers
What is the current behavior? (You can also link to an open issue here)
Only tags like "gpl" or "bsd" are used without more information which version of the license is used
What is the new behavior (if this is a feature change)? If possible add a screenshot.
SPDX License identifier are used (e.g. GPL-2.0-or-later)
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No breaking change
Other information:
In one or two license information the SPDX conform "AND" or "OR" is used to express that both licenses are used or one license can be selected. This is currently not further used.
There are still some license information missing, this first PR aims at transferring the current identified licenses and add a few ones. More can be identified in the future.