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/language | |
| 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/language')
| -rw-r--r-- | doc/manual/src/language/derivations.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual/src/language/derivations.md b/doc/manual/src/language/derivations.md index 3391ec0d8..043a38191 100644 --- a/doc/manual/src/language/derivations.md +++ b/doc/manual/src/language/derivations.md @@ -1,7 +1,7 @@ # Derivations The most important built-in function is `derivation`, which is used to -describe a single derivation (a build action). It takes as input a set, +describe a single derivation (a build task). It takes as input a set, the attributes of which specify the inputs of the build. - There must be an attribute named [`system`]{#attr-system} whose value must be a |