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

revert to "build plan" in overview diagram

Browse source 
this displays correct composition again. build inputs and build results
are not part of build plans in terms of data objects.

also this is a much less complicated setup. this will be the first
impression of architecture, and we want to get it right.
This commit is contained in:
Valentin Gagarin 2022-05-20 23:46:34 +02:00
parent 25926c5fc6
commit 2303f84a68
1 changed files with 16 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
doc/manual/src/architecture/architecture.md
View file

@ -8,19 +8,22 @@ It should help users understand why Nix behaves as it does, and it should help d
Nix consists of hierarchical [layers](https://en.m.wikipedia.org/wiki/Multitier_architecture#Layers).
```
[ commmand line interface ]--------+
| |
| evaluates | manages
V |
[ configuration language ] |
| |
+-------------------------------|---------------------V-----------+
| store | evaluates to |
| .............................V............................... |
| : build plan : |
| : referenced by builds : |
| : [ build input ] --> [ build task ] --> [ build result ] : |
| :...........................................................: |
+-----------------------------------------------------------------+
| Nix |
| [ commmand line interface ]------, |
| | | |
| evaluates | |
| | manages |
| V | |
| [ configuration language ] | |
| | | |
| +-----------------------------|-------------------V-----------+ |
| | store evaluates to | |
| | | | |
| | referenced by V builds | |
| | [ build input ] ---> [ build plan ] ---> [ build result ] | |
| | | |
| +-------------------------------------------------------------+ |
+-----------------------------------------------------------------+
```