| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 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 | |||
| 2022-08-04 | address Nix language consistently as configuration language | Valentin Gagarin | |
| 2022-08-04 | remove separate meta-section, add architecture diagram | Valentin Gagarin | |
| the diagram is a first approximation and only covers that same section. of course there is much more going on, and other features should at some point also be illustrated. we also have to think about presentation format and technicalities behind it. the manual has to render to `man`, but we may want something more refined for web view. | |||
| 2022-08-04 | reword introductory section | Valentin Gagarin | |
| there should be a meta section for each chapter to give motivation of the presented structure. the structure itself is visible from the table of contents. | |||
| 2022-08-04 | remove sentence for chapter transition | Valentin Gagarin | |
| idea: sections could be read in different orders by linking them in different ways (e.g. depth-first or breadth-first). adding hard-coded transitions makes that confusing. | |||
| 2022-08-04 | Apply suggestions from code review | John Ericson | |
| Co-authored-by: Valentin Gagarin <valentin@fricklerhandwerk.de> | |||
| 2022-08-04 | do not mention implementation details | Valentin Gagarin | |
| Co-authored-by: John Ericson <git@JohnEricson.me> | |||
| 2022-08-04 | correctly use comma for nesting | Valentin Gagarin | |
| Co-authored-by: John Ericson <git@JohnEricson.me> | |||
| 2022-08-04 | indicate sequence with "then" | Valentin Gagarin | |
| Co-authored-by: John Ericson <git@JohnEricson.me> | |||
| 2022-08-04 | only use generic build system terminology | Valentin Gagarin | |
| we will use a translation table to introduce nix-specific terms | |||
| 2022-08-04 | reword overview with clear terminology | Valentin Gagarin | |
| trying to capture alternative terms in one go here, mirroring everyday use: derivation - build plan realise - execute build there will be more of that sort. | |||
| 2022-08-04 | Add draft "Rosetta stone" by @fricklerhandwerk and stub commentary | John Ericson | |
| The idea and most of the execution are @fricklerhandwerk's. I changed a few things best I could based on @edolstra's corrections, and a Bazel glossary. Valentin Gagarin <valentin@fricklerhandwerk.de> | |||
| 2022-08-04 | Make refernces sneak preview more concise | John Ericson | |
| 2022-08-04 | Improve store objects session more | John Ericson | |
| 2022-08-04 | Include abstract syntax based on the thesis for FSOs | John Ericson | |
| See https://edolstra.github.io/pubs/phd-thesis.pdf, page 91. | |||
| 2022-08-04 | store objects, better opining sentances | John Ericson | |
| 2022-08-04 | Improve store path section | John Ericson | |
| 2022-08-04 | Relocability -> relocation in store object title | John Ericson | |
| 2022-08-04 | Improve store object section | John Ericson | |
| In particular, Nix is *not* like Git, so that needs to be fixed. | |||
| 2022-08-04 | doc: File system data -> file system object, to match Nix | John Ericson | |
| 2022-08-04 | Rename files after store entry -> store object rename | John Ericson | |
| 2022-08-04 | doc: Store entry -> store object | John Ericson | |
| This matches the terminology in Eelco's thesis. | |||
| 2022-08-04 | Update doc/manual/src/design/store/drvs/drvs.md | John Ericson | |
| Co-authored-by: Matthieu Coudron <teto@users.noreply.github.com> | |||
| 2022-08-04 | Update doc/manual/src/design/overview.md | John Ericson | |
| Co-authored-by: Valentin Gagarin <valentin@fricklerhandwerk.de> | |||
| 2022-08-04 | Update doc/manual/src/design/overview.md | John Ericson | |
| Co-authored-by: Valentin Gagarin <valentin@fricklerhandwerk.de> | |||
| 2022-08-04 | Update doc/manual/src/design/overview.md | John Ericson | |
| Co-authored-by: Valentin Gagarin <valentin@fricklerhandwerk.de> | |||
| 2022-08-04 | Fix stub file's name | John Ericson | |
| 2022-08-04 | Start on the derivations section | John Ericson | |
| 2022-08-04 | Move the bits on relocating store entires to the end | John Ericson | |
| They are too advanced for up front. | |||
| 2022-08-04 | Apply suggestions from code review | John Ericson | |
| 2022-08-04 | Flesh out TOC | John Ericson | |
| 2022-08-04 | Briefly describe the digest of a store path | John Ericson | |
| 2022-08-04 | WIP: Document the design of Nix | John Ericson | |
| The current docs are all "how to do things" and no "what is Nix" or "why are things the way they are". I see lots of misconception on the wider internet, and I also think we would benefit from a "living document" to answer some questions people currently turn to the thesis for. I think a new section of the manual can address all these issues. | |||
| 2022-08-03 | Merge pull request #6846 from fricklerhandwerk/values | Théophane Hufschmitt | |
| manual: use subheadings for primitive types | |||
 |
index : lix | |
| User & |
| aboutsummaryrefslogtreecommitdiff |