aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/src/architecture
diff options
context:
space:
mode:
authorValentin Gagarin <valentin.gagarin@tweag.io>2022-05-12 12:30:28 +0200
committerValentin Gagarin <valentin.gagarin@tweag.io>2022-08-04 12:37:47 +0200
commit689b32a543240db992c9e8240401f32bd39e6736 (patch)
treeee657e2ef9107123bff54fe7b8c18a989e947ce6 /doc/manual/src/architecture
parent2a8532fb61ba2b988448e93f5074590e40df7e04 (diff)
clarify relation of tasks and plans
Diffstat (limited to 'doc/manual/src/architecture')
-rw-r--r--doc/manual/src/architecture/architecture.md19
1 files changed, 9 insertions, 10 deletions
diff --git a/doc/manual/src/architecture/architecture.md b/doc/manual/src/architecture/architecture.md
index 407e8d0f8..e8d87f8ae 100644
--- a/doc/manual/src/architecture/architecture.md
+++ b/doc/manual/src/architecture/architecture.md
@@ -13,21 +13,21 @@ Nix consists of hierarchical [layers](https://en.m.wikipedia.org/wiki/Multitier_
| evaluates | manages
V |
[ configuration language ] |
- | V
-+-------------------------------|---------------------------------+
-| store | |
-| | evaluates to |
-| | |
-| referenced by V builds |
-| [ build input ] --> [ build task ] --> [ build result ] |
-| |
+ | |
++-------------------------------|---------------------V-----------+
+| store | evaluates to |
+| .............................V............................... |
+| : build plan : |
+| : referenced by builds : |
+| : [ build input ] --> [ build task ] --> [ build result ] : |
+| :...........................................................: |
+-----------------------------------------------------------------+
```
At the top is the *command line interface*, translating from invocations of Nix executables to interactions with the underlying layers.
Below that is the *Nix language*, a [purely functional](https://en.m.wikipedia.org/wiki/Purely_functional_programming) configuration language.
-It is used to compose expressions which ultimately evaluate to self-contained *build tasks*, used to derive *build results* from referenced *build inputs*.
+It is used to compose expressions which ultimately evaluate to self-contained *build plans*, made up *build tasks* used to derive *build results* from referenced *build inputs*.
::: {.note}
The Nix language itself does not have a notion of *packages* or *configurations*.
@@ -40,4 +40,3 @@ The command line and Nix language are what users interact with most.
Underlying everything is the *Nix store*, a mechanism to keep track of build tasks, data, and references between them.
It can also execute *build instructions*, captured in the build tasks, to produce new data.
-A series of build tasks is a *build plan*.