wroclaw-git-backups/nix
1
0
Fork 0
mirror of https://github.com/NixOS/nix synced 2025-07-07 14:21:48 +02:00
Code Activity

manual: Edit

Browse source
This commit is contained in:
Robert Hensing 2025-03-03 19:09:24 +01:00
parent 2aa6e0f084
commit 1e00d14c29
8 changed files with 55 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/manual/source/store/derivation/outputs/content-address.md
View file

@ -12,7 +12,7 @@ Given the method, the output's name (computed from the derivation name and outpu
## Fixed-output content-addressing {#fixed}
In this case the content-address of the *fixed* in advanced by the derivation itself.
In this case the content address of the *fixed* in advanced by the derivation itself.
In other words, when the derivation has finished [building](@docroot@/store/building.md), and the provisional output' content-address is computed as part of the process to turn it into a *bona fide* store object, the calculated content address must much that given in the derivation, or the build of that derivation will be deemed a failure.
The output spec for an output with a fixed content addresses additionally contains:
@ -159,7 +159,7 @@ A *determinstic* content-addressing derivation should produce outputs with the s
### Floating versus Fixed
While the destinction between content- and input-addressing is one of *mechanism*, the distinction between fixed and floating content addression is more one of *policy*.
While the distinction between content- and input-addressing is one of *mechanism*, the distinction between fixed and floating content addressing is more one of *policy*.
A fixed output that passes its content address check is just like a floating output.
It is only in the potential for that check to fail that they are different.

2
doc/manual/source/store/derivation/outputs/input-address.md
View file

@ -3,7 +3,7 @@
[input addressing]: #input-addressing
"Input addressing" means the address the store object by the *way it was made* rather than *what it is*.
That is to say, an input-addressed output's store path is a function not of the output itself, but the derivation that produced it.
That is to say, an input-addressed output's store path is a function not of the output itself, but of the derivation that produced it.
Even if two store paths have the same contents, if they are produced in different ways, and one is input-addressed, then they will have different store paths, and thus guaranteed to not be the same store object.
<!---