mergify[bot]
aabe327111
Merge pull request #13646 from NixOS/mergify/bp/2.29-maintenance/pr-13382
...
Update docs (backport #13382 )
2025-07-31 02:11:49 +00:00
mergify[bot]
012f429104
Merge pull request #13639 from NixOS/mergify/bp/2.29-maintenance/pr-13373
...
Fix typo (backport #13373 )
2025-07-31 01:52:55 +00:00
mergify[bot]
830dfc3b60
Merge pull request #13641 from NixOS/mergify/bp/2.29-maintenance/pr-13372
...
Fix broken link (backport #13372 )
2025-07-31 01:49:41 +00:00
Nikita Krasnov
ceb4d561fa
Update docs
...
(cherry picked from commit 785f3867fd
2025-07-30 13:00:38 +00:00
Nikita Krasnov
5d58ab8042
Fix broken link
...
(cherry picked from commit da76bc0cac
2025-07-30 12:59:29 +00:00
Nikita Krasnov
27a8b457b8
Fix typo
...
(cherry picked from commit 86dda9884a
2025-07-30 12:58:23 +00:00
Peder Bergebakken Sundt
94723d5b72
docs: fix duplicate anchor
...
`#deriving-path-encoding` is defined in two places, I _think_ this is the correct one to change.
(cherry picked from commit 4c50cf798e
2025-07-30 11:53:57 +00:00
Peder Bergebakken Sundt
6fc6db3496
docs: remove lexical illusions detected with write-good
...
I made this this non-markdown aware tool somewhat behave with some cursed fd+pandoc invocations
(cherry picked from commit ea5302c4a2
2025-05-16 15:56:26 +00:00
Jörg Thalheim
a70140b55a
fix various typos in docs
2025-05-14 21:29:17 +02:00
John Ericson
b287438476
Document more references concepts
2025-05-14 12:57:06 -04:00
Sergei Zimmerman
20a724d131
docs: Fix miscellaneous typos and formatting issues
2025-05-13 22:20:11 +00:00
Farid Zakaria
33493b9ead
Fix minor documentation typos
...
Was reading the store chapter and came across a few small typos
and edits.
2025-03-07 23:07:03 -08:00
Robert Hensing
1e00d14c29
manual: Edit
2025-03-03 19:09:24 +01:00
John Ericson
2aa6e0f084
Expand manual on derivation outputs
...
Note, this includes some text adapted from from Eelco's dissertation
2025-02-27 02:13:36 -05:00
John Ericson
cafefed421
Rename to "content-address*ing* derivation"
...
"content-address*ed*" derivation is misleading because all derivations
are *themselves* content-addressed. What may or may not be
content-addressed is not derivation itself, but the *output* of the
derivation.
The outputs are not *part* of the derivation (for then the derivation
wouldn't be complete before we built it) but rather separate entities
produced by the derivation.
"content-adddress*ed*" is not correctly because it can only describe
what the derivation *is*, and that is not what we are trying to do.
"content-address*ing*" is correct because it describes what the
derivation *does* --- it produces content-addressed data.
2025-02-10 01:12:56 -05:00
John Ericson
e80d333777
Document Store Derivations and Deriving Paths ( #12290 )
...
This is a big step documenting the store layer on its own, separately from the evaluator (and `builtins.derivation`).
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
2025-02-10 01:30:07 +00:00
Emil Petersen
78aedda6bd
Update content-address.md ( #11771 )
...
Correct a few typos. Make explicit that FSO acronym refers to File System Object.
2024-10-30 23:31:03 +00:00
John Ericson
eb7d7780b1
Rename doc/manual{src -> source}
...
This is needed to avoid this
https://github.com/mesonbuild/meson/issues/13774 when we go back to
making our subproject directory `src`.
2024-10-14 11:21:24 -04:00
