Skip to content

Commit

Permalink
added missing peroid, removed superfluous period. reminded reader wha…
Browse files Browse the repository at this point in the history
…t derivations are
  • Loading branch information
ellyxir committed Nov 7, 2024
1 parent 8814c61 commit 5171eef
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions source/tutorials/nix-language.md
Original file line number Diff line number Diff line change
Expand Up @@ -1767,18 +1767,19 @@ For historical reasons, some of the functions in `pkgs.lib` are equivalent to [`
So far we have only covered what we call *pure expressions*:
declaring data and transforming it with functions.

In practice, describing derivations requires observing the outside world.
In practice, describing derivations requires observing the outside world. Recall that derivations are
precise descriptions of how contents of existing files are used to derive new files. We discuss [](derivations)futher in the tuturial.

There is only one impurity in the Nix language that is relevant here:
reading files from the file system as *build inputs*
reading files from the file system as *build inputs*.

Build inputs are files that derivations refer to in order to describe how to derive new files.
When run, a derivation will only have access to explicitly declared build inputs.

The only way to specify build inputs in the Nix language is explicitly with:

- File system paths
- Dedicated functions.
- Dedicated functions

Nix and the Nix language refer to files by their content hash. If file contents are not known in advance, it's unavoidable to read files during expression evaluation.

Expand Down

0 comments on commit 5171eef

Please sign in to comment.