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: 7 -> 10 #85034

Closed
wants to merge 3 commits into from
Closed

llvmPackages: 7 -> 10 #85034

wants to merge 3 commits into from

Conversation

bqv
Copy link
Contributor

@bqv bqv commented Apr 11, 2020

Motivation for this change

Testing the effect of this change

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@grahamc
Copy link
Member

grahamc commented Apr 11, 2020

@ofborg eval

Copy link
Member

@primeos primeos left a comment

Choose a reason for hiding this comment

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

Thanks for this PR, but the approach might unfortunately a bit too simplistic (though I haven't had a closer look yet).

Why on earth is llvmPackages still pointing at 7?

Most likely because it's a lot of work to switch the default. You basically need to rebuild all reverse dependencies (could easily be a few thousand packages, but I haven't actually checked this), determine which ones break due to this changes, and fix the breakages and/or notify the maintainers.

Testing this change probably requires a beefy machine for nixpkgs-review or a dedicated Hydra jobset.

Regarding this PR: The commits should be squashed (but this can also be done when merging) and after determining the number of rebuilds this causes it might have to go into staging (which seems like a good idea anyway, but in case it causes only a few rebuilds as we built most packages with GCC it might theoretically be ok for master as well).

Anyway this is basically just a quick FYI / heads up that nixpkgs-review is a requirement for this PR (or a Hydra jobset if this causes too many rebuilds).

@bqv
Copy link
Contributor Author

bqv commented Apr 11, 2020

Thanks. My machine probably isn't strong enough to run that! This was entirely a test to see how many packages would be affected by this, since at a glance, most that use llvmPackages seem to pin a particular version anyway - I never intended for this to be merged :)

@bqv bqv closed this Apr 11, 2020
@bqv bqv deleted the llvm10 branch April 17, 2020 20:24
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

3 participants