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

update description of "store derivation" in installables section

Browse source 
a store derivation is not a store path itself, it has a store path.
This commit is contained in:
Valentin Gagarin 2022-12-20 15:26:05 +01:00
parent 62f4f883a7
commit 3a66d82e1d
2 changed files with 9 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -144,7 +144,9 @@
references `R` then `R` is also in the closure of `P`.
- [output path]{#gloss-output-path}\
A store path produced by a derivation.
A [store path] produced by a [derivation].
[output path]: #gloss-output-path
- [deriver]{#gloss-deriver}\
The deriver of an *output path* is the store

12
src/nix/nix.md
View file

@ -115,12 +115,12 @@ the Nix store. Here are the recognised types of installables:
* **Store derivations**: `/nix/store/p7gp6lxdg32h4ka1q398wd9r2zkbbz2v-hello-2.10.drv`
Store derivations are store paths with extension `.drv` and are a
low-level representation of a build-time dependency graph used
internally by Nix. By default, if you pass a store derivation to a
`nix` subcommand, it will operate on the *output paths* of the
derivation. For example, `nix path-info` prints information about
the output paths:
Store derivations are a low-level, internal representation of build tasks in Nix, and have store paths with extension `.drv`.
By default, if you pass the path to a store derivation to a `nix` subcommand, the command will operate on the [output path]s of the derivation.
[output path]: ../../glossary.md#gloss-output-path
For example, `nix path-info` prints information about the output paths:
```console
# nix path-info --json /nix/store/p7gp6lxdg32h4ka1q398wd9r2zkbbz2v-hello-2.10.drv