-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
{ed,gzip,gawk,gnugrep}: Add bash to buildInputs #314660
{ed,gzip,gawk,gnugrep}: Add bash to buildInputs #314660
Conversation
You are modifying four different packages kept by different people. Please, do one commit per package (no need for a new PR), so we can know what to bisect in a future bisection adventure. P.S.: why the hell so many bootstrap packages has literally no maintainers? We are forcing new contributors to be maintainers of the leaf packages they want to add, but for something literally fundamental as the system bootstrap, maintainers list is empty? |
bdf747e
to
cb543d7
Compare
I've split up the commit. Do you need me to take ownership of any of these packages? |
For now there is no need to keep maintainership of them. I will create a Nixpkgs team later this week to formalize this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to use runtimeShell
for this, or must these scripts use bash
in particular?
cb543d7
to
cd9de46
Compare
I didn't know about runtimeShell! I've changed it. |
This package distributes shell scripts in /bin. Its shebangs are always patched to a /nix/store shell, but by default, they are patched to use the stdenv's shell, which during bootstrap is build in the previous stdenv. By using runtimeShell from the current stdenv, we can shorten the FreeBSD bootstrap process significantly.
This package distributes shell scripts in /bin. Its shebangs are always patched to a /nix/store shell, but by default, they are patched to use the stdenv's shell, which during bootstrap is build in the previous stdenv. By using runtimeShell from the current stdenv, we can shorten the FreeBSD bootstrap process significantly.
This package distributes shell scripts in /bin. Its shebangs are always patched to a /nix/store shell, but by default, they are patched to use the stdenv's shell, which during bootstrap is build in the previous stdenv. By using runtimeShell from the current stdenv, we can shorten the FreeBSD bootstrap process significantly.
This package distributes shell scripts in /bin. Its shebangs are always patched to a /nix/store shell, but by default, they are patched to use the stdenv's shell, which during bootstrap is build in the previous stdenv. By using runtimeShell from the current stdenv, we can shorten the FreeBSD bootstrap process significantly.
cd9de46
to
125d947
Compare
Description of changes
part of #296581
These packages distribute shell scripts in /bin. Their shebangs are always patched to a /nix/store bash, but by default, they are patched to use the stdenv's shell, which during bootstrap is build in the previous stdenv. By using bash from the current stdenv, we can shorten the FreeBSD bootstrap process significantly.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.