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
SPDX License List 3.2 available #5282
Comments
Would be nice to use this opportunity to document the process of upgrading to a new license list version. |
phadej
changed the title
SPDX License List 3.1 available
SPDX License List 3.2 available
Jul 29, 2018
Seems that procrastinating pays off sometimes: When |
@phadej have you figured out how to handle the |
I think I'll just make Parsec LicenseId case on version (use different auxiliary lookup map), so we can have only non-deprecated LicenseId's in use
The challenge is to engineer the codegen so it doesn't torture GHC too much. I think
- single large LicenseId enum, but
- separate mkLicenseId's per Cabal-spec/SPDX license list version
…Sent from my iPhone
On 29 Jul 2018, at 23.23, Herbert Valerio Riedel ***@***.***> wrote:
@phadej have you figured out how to handle the cabal-version: spec-version <-> SPDX list spec version correlation?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://www.mail-archive.com/spdx-legal@lists.spdx.org/msg01771.html
The text was updated successfully, but these errors were encountered: