diff options
| author | Valentin Gagarin <valentin.gagarin@tweag.io> | 2022-11-06 12:25:21 +0100 |
|---|---|---|
| committer | Valentin Gagarin <valentin.gagarin@tweag.io> | 2022-11-06 13:28:18 +0100 |
| commit | f7ab93b0685b653c60b86540639a42b03389c90b (patch) | |
| tree | 1d2ea66f448d9f80a02a8e22a25100fd2309082b /doc/manual/src/introduction.md | |
| parent | 499e99d099ec513478a2d3120b2af3a16d9ae49d (diff) | |
manual: build action -> build task
after discussing this with multiple people, I'm convinced that "build
task" is more precise: a derivation is not an action, but inert until it
is built. also it's easier to pronounce.
proposal: use "build task" for the generic concept "description of how
to derive new files from the contents of existing files". then it will
be easier to distinguish what we mean by "derivation" (a specific data
structure and Nix language value type) and "store derivation" (a
serialisation of a derivation into a file in the Nix store).
Diffstat (limited to 'doc/manual/src/introduction.md')
| -rw-r--r-- | doc/manual/src/introduction.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual/src/introduction.md b/doc/manual/src/introduction.md index d87487a07..b54346db8 100644 --- a/doc/manual/src/introduction.md +++ b/doc/manual/src/introduction.md @@ -104,7 +104,7 @@ a currently running program. Packages are built from _Nix expressions_, which is a simple functional language. A Nix expression describes everything that goes -into a package build action (a “derivation”): other packages, sources, +into a package build task (a “derivation”): other packages, sources, the build script, environment variables for the build script, etc. Nix tries very hard to ensure that Nix expressions are _deterministic_: building a Nix expression twice should yield the same |