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

llvmPackages: add asl20-llvm to licenses for v19+ #314347

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rrbutani
Copy link
Contributor

@rrbutani rrbutani commented May 24, 2024

Description of changes

As per llvm/llvm-project#92394 contributions made after June 1st, 2024 are licensed exclusively under Apache-2.0 WITH LLVM-exception rather than dual licensed.

As per this post, this change is timed so that it only affects version 19 and newer.

If I'm understanding correctly, I think this means we should add licenses.asl20-llvm to llvm_meta.license for release_version >= 19.

Previously: #217906.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

As per llvm/llvm-project#92394 contributions made after June 1st, 2024 are
licensed exclusively under `Apache-2.0 WITH LLVM-exception` rather than dual
licensed.

As per this post, this change is timed so that it only affects version 19 and
newer: https://discourse.llvm.org/t/relicensing-next-step-dropping-requirement-to-contribute-also-under-the-legacy-license/78351
@rrbutani rrbutani requested a review from alyssais May 24, 2024 18:58
@rrbutani rrbutani added the 6.topic: llvm/clang Issues related to llvmPackages, clangStdenv and related label May 27, 2024
Copy link
Member

@RossComputerGuy RossComputerGuy left a comment

Choose a reason for hiding this comment

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

Sounds good though wouldn't a better fit be with an LLVM git update PR rather than it's own PR?

@rrbutani
Copy link
Contributor Author

rrbutani commented May 27, 2024

wouldn't a better fit be with an LLVM git update PR rather than it's own PR?

I didn't want us to forget to make this change and I wanted another pair of eyes on this change specifically — I've made mistakes here before.

@RossComputerGuy
Copy link
Member

I didn't want us to forget to make this change and I wanted another pair of eyes on this change specifically — I've made mistakes here before.

Sounds good, LGTM. Meanwhile, I'll try to fix the latest LLVM git update so we can merge that ASAP. Hopefully that'll make LLVM 19 smooth sailing when that releases in like a month or two.

@rrbutani
Copy link
Contributor Author

rrbutani commented Aug 6, 2024

@alyssais: friendly ping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants