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

kernel: build initrd and modules tree locally #69386

Closed

Conversation

ivan
Copy link
Member

@ivan ivan commented Sep 24, 2019

Motivation for this change

morph was spending too much time building these remotely. I confirmed that it started building locally.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • 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 nix-review --run "nix-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.
Notify maintainers

cc @thoughtpolice

If accepted, please cherry-pick to 19.09 or let me know you want a backport PR.

@grahamc
Copy link
Member

grahamc commented Sep 24, 2019

I'm not sure. For example, if I'm building a dozen systems worth, it is very worth it to me to build the initrds remotely. Especially since the initrds do take a good bit of resources to compute. I think typically the "prefer local" builds are much more trivial than an initrd.

Not a -1.

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

Successfully merging this pull request may close these issues.

None yet

2 participants