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.

Sign up for GitHub

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

Jump to bottom

Licenses that can't be matched should be flagged as custom #59

Open
schuylermartin45 opened this issue May 14, 2024 · 0 comments
Open

Licenses that can't be matched should be flagged as custom #59

schuylermartin45 opened this issue May 14, 2024 · 0 comments
Labels
SPDX Related to SPDX licensing validation v0 to v1 recipe conversion Issues with our v0 -> v1 recipe upgrade tooling

Comments

@schuylermartin45
Copy link
Collaborator

Licenses we can't match to a known SPDX compliant license should be flagged as custom per the SPDX spec. This should make rattler-build happy with any remaining license files we can't automatically fix. Some may actually be custom licenses.
@schuylermartin45 schuylermartin45 added v0 to v1 recipe conversion Issues with our v0 -> v1 recipe upgrade tooling SPDX Related to SPDX licensing validation labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
SPDX Related to SPDX licensing validation v0 to v1 recipe conversion Issues with our v0 -> v1 recipe upgrade tooling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@schuylermartin45