| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2022-08-04 | build rule -> build task | Valentin Gagarin | |
| closer to "build systems a la carte", satisfies all other complaints | |||
| 2022-08-04 | build step -> build rule | Valentin Gagarin | |
| "step" sounds atomic, while "rule" hints at internal structure, which in our case consists of mapping inputs to outputs using build instructions. | |||
| 2022-08-04 | remove incomplete section: input/content-addressing | Valentin Gagarin | |
| 2022-08-04 | remove incomplete section: nix archives | Valentin Gagarin | |
| 2022-08-04 | remove incomplete section: content-addressed objects | Valentin Gagarin | |
| 2022-08-04 | remove incomplete section: relocatability | Valentin Gagarin | |
| 2022-08-04 | remove incomplete section: related work | Valentin Gagarin | |
| 2022-08-04 | remove incomplete section: building | Valentin Gagarin | |
| 2022-08-04 | Fix rel path in doc | John Ericson | |
| 2022-08-04 | reword details on keeping closure property | Valentin Gagarin | |
| 2022-08-04 | add motivation for references | Valentin Gagarin | |
| 2022-08-04 | stores can also delete objects | Valentin Gagarin | |
| 2022-08-04 | formalize file system objects | Valentin Gagarin | |
| convention: describe every data type in prose, and illustrate with a class diagram, and a textual representation of an abstract data type. right now we save ourselves the trouble of doing class diagrams, we can add them later. but they are important. | |||
| 2022-08-04 | reword section on references | Valentin Gagarin | |
| use file Contents instead of Data, as that flows more naturally in the prose. simplify explanation of the idea behind scanning for store paths remove references to unfinished sections. | |||
| 2022-08-04 | reword file system objects | Valentin Gagarin | |
| - use singular for the "class" - more consistency in type definition - minor fixes in wording | |||
| 2022-08-04 | move git comparison to related work | Valentin Gagarin | |
| it should be pulled out of the branch before we go for merging | |||
| 2022-08-04 | component -> store object, realisation -> build | Valentin Gagarin | |
| 2022-08-04 | build instrcution: Task -> function | Valentin Gagarin | |
| 2022-08-04 | revert build plan/step distinction, reorder rows | Valentin Gagarin | |
| 2022-08-04 | reword introduction to rosetta stone, add links | Valentin Gagarin | |
| attempt to explain used and documented terminology, as well as how the declarative programming paradigm relates to building software. in the future one could highlight encouraged terms to shape future material into higher consistency. | |||
| 2022-08-04 | associated operations are not collected | Valentin Gagarin | |
| Co-authored-by: John Ericson <git@JohnEricson.me> | |||
| 2022-08-04 | fix grammar | Valentin Gagarin | |
| Co-authored-by: John Ericson <git@JohnEricson.me> | |||
| 2022-08-04 | add concrete store examples, reword note on file system | Valentin Gagarin | |
| 2022-08-04 | reword section on Nix store | Valentin Gagarin | |
| 2022-08-04 | design -> architecture, add motivation | Valentin Gagarin | |
| following ideas found in Architecture of Gazelle[1] [1]: https://github.com/bazelbuild/bazel-gazelle/blob/56d35f8db086bb65ef876f96f7baa7b71516daf8/Design.rst | |||
 |
index : lix | |
| User & |
| aboutsummaryrefslogtreecommitdiff |