Skip to content
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

Add some categorizations for GCC exception 3.1 #163

Merged
merged 3 commits into from
Dec 28, 2023

Conversation

fviernau
Copy link
Member

See individual commits.

Signed-off-by: Frank Viernau <frank_viernau@epam.com>
Signed-off-by: Frank Viernau <frank_viernau@epam.com>
The updated content was generated by [1].

[1] ./gradlew generateLicenseClassifications

Signed-off-by: Frank Viernau <frank_viernau@epam.com>
@fviernau fviernau requested review from a team as code owners December 28, 2023 09:35
@fviernau fviernau enabled auto-merge (rebase) December 28, 2023 09:35
@@ -1082,6 +1082,11 @@ categorizations:
- "copyleft-limited"
- "include-in-notice-file"
- "include-source-code-offer-in-notice-file"
- id: "GPL-3.0-only WITH GCC-exception-3.1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just FYI, I was thinking (with @willebra and others) about actually allowing to classify exceptions on their own. There's nothing built into ORT that currently prohibits that. And it would have the advantage that you don't need to classify e.g. GCC-exception-3.1 with every license it can be combined with, but only GCC-exception-3.1 on its own. Then, taking into account ORT's exception mapping, you'd know the applicable licenses, and could handle the combination of licenses with exception only in rules, but not yet in the classification.

@fviernau fviernau merged commit bae772f into main Dec 28, 2023
2 checks passed
@fviernau fviernau deleted the scancode-license-categorize-some-gcc-exceptions branch December 28, 2023 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants