eisfunke/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity

add anchor to builder

Browse source
This commit is contained in:
Valentin Gagarin 2023-07-13 22:17:51 +02:00
parent d50f116421
commit 0cd8f36644
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/manual/src/command-ref/nix-store/realise.md
View file

@ -17,7 +17,7 @@ Each of *paths* is processed as follows:
2. Realise its [output paths]: 2. Realise its [output paths]:
- Try to fetch from [substituters] the [store objects] associated with the output paths in the store derivation's [closure]. - Try to fetch from [substituters] the [store objects] associated with the output paths in the store derivation's [closure].
- With [content-addressed derivations] (experimental): Determine the output paths to realise by querying build certificates in the [Nix database]. - With [content-addressed derivations] (experimental): Determine the output paths to realise by querying build certificates in the [Nix database].
- For any store paths that cannot be substituted, produce the required store objects by first realising all outputs of the derivation's dependencies and then running the derivation's build instructions. - For any store paths that cannot be substituted, produce the required store objects by first realising all outputs of the derivation's dependencies and then running the derivation's [`builder`](@docroot@/language/derivations.md#attr-builder) executable.
- Otherwise: Try to fetch the associated [store objects] in the paths' [closure] from [substituters]. - Otherwise: Try to fetch the associated [store objects] in the paths' [closure] from [substituters].
If no substitutes are available and no store derivation is given, realisation fails. If no substitutes are available and no store derivation is given, realisation fails.

2
doc/manual/src/glossary.md
View file

@ -33,7 +33,7 @@
Ensure a [store path] is [valid][validity]. Ensure a [store path] is [valid][validity].
This means either running the `builder` executable as specified in the corresponding [derivation] or fetching a pre-built [store object] from a [substituter]. This means either running the [`builder`](@docroot@/language/derivations.md#attr-builder) executable as specified in the corresponding [derivation] or fetching a pre-built [store object] from a [substituter].
See [`nix-build`](./command-ref/nix-build.md) and [`nix-store --realise`](@docroot@/command-ref/nix-store/realise.md). See [`nix-build`](./command-ref/nix-build.md) and [`nix-store --realise`](@docroot@/command-ref/nix-store/realise.md).

2
doc/manual/src/language/derivations.md
View file

@ -17,7 +17,7 @@ the attributes of which specify the inputs of the build.
string. This is used as a symbolic name for the package by string. This is used as a symbolic name for the package by
`nix-env`, and it is appended to the output paths of the derivation. `nix-env`, and it is appended to the output paths of the derivation.
- There must be an attribute named `builder` that identifies the - There must be an attribute named [`builder`]{#attr-builder} that identifies the
program that is executed to perform the build. It can be either a program that is executed to perform the build. It can be either a
derivation or a source (a local file reference, e.g., derivation or a source (a local file reference, e.g.,
`./builder.sh`). `./builder.sh`).