diff options
author | Eelco Dolstra <edolstra@gmail.com> | 2020-07-24 11:43:44 +0200 |
---|---|---|
committer | Eelco Dolstra <edolstra@gmail.com> | 2020-07-24 11:43:44 +0200 |
commit | 8d0b311a1ccd0aef49c6f272aad4ecb5105b285a (patch) | |
tree | 98869179b5348d99f846b7ae74a2cf8d6362c18f /doc/manual/src/expressions/build-script.md | |
parent | a71d1cedffe17ea4dd6a48c12cf5b9323ca6114c (diff) |
Get rid of footnotes
Markdown doesn't support them.
Diffstat (limited to 'doc/manual/src/expressions/build-script.md')
-rw-r--r-- | doc/manual/src/expressions/build-script.md | 10 |
1 files changed, 3 insertions, 7 deletions
diff --git a/doc/manual/src/expressions/build-script.md b/doc/manual/src/expressions/build-script.md index f922182c2..57222de85 100644 --- a/doc/manual/src/expressions/build-script.md +++ b/doc/manual/src/expressions/build-script.md @@ -19,10 +19,9 @@ steps to elucidate what a builder does. It performs the following steps: 1. When Nix runs a builder, it initially completely clears the environment (except for the attributes declared in the derivation). - For instance, the `PATH` variable is empty\[1\]. This is done to - prevent undeclared inputs from being used in the build process. If - for example the `PATH` contained `/usr/bin`, then you might - accidentally use `/usr/bin/gcc`. + This is done to prevent undeclared inputs from being used in the + build process. If for example the `PATH` contained `/usr/bin`, then + you might accidentally use `/usr/bin/gcc`. So the first step is to set up the environment. This is done by calling the `setup` script of the standard environment. The @@ -67,6 +66,3 @@ If you are wondering about the absence of error checking on the result of various commands called in the builder: this is because the shell script is evaluated with Bash's `-e` option, which causes the script to be aborted if any command fails without an error check. - -1. Actually, it's initialised to `/path-not-set` to prevent Bash from - setting it to a default value. |