mirror of
https://github.com/NixOS/nix
synced 2025-06-25 06:31:14 +02:00
document store objects in terms of their constituent parts
this also rephrases the introductory sentence to be more general, in order to avoid the same word being repeated in short succession.
This commit is contained in:
parent
12f9719162
commit
4ba8b182be
5 changed files with 16 additions and 4 deletions
|
@ -63,7 +63,7 @@ The command line interface and Nix expressions are what users deal with most.
|
|||
> The Nix language itself does not have a notion of *packages* or *configurations*.
|
||||
> As far as we are concerned here, the inputs and results of a build plan are just data.
|
||||
|
||||
Underlying the command line interface and the Nix language evaluator is the [Nix store](../glossary.md#gloss-store), a mechanism to keep track of build plans, data, and references between them.
|
||||
Underlying the command line interface and the Nix language evaluator is the [Nix store](../store/index.md), a mechanism to keep track of build plans, data, and references between them.
|
||||
It can also execute build plans to produce new data, which are made available to the operating system as files.
|
||||
|
||||
A build plan itself is a series of *build tasks*, together with their build inputs.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue