forked from lix-project/lix
add subsections to table of contents
This commit is contained in:
parent
c345345dee
commit
def80d5777
|
@ -17,7 +17,13 @@
|
||||||
- [Upgrading Nix](installation/upgrading.md)
|
- [Upgrading Nix](installation/upgrading.md)
|
||||||
- [Architecture](architecture/architecture.md)
|
- [Architecture](architecture/architecture.md)
|
||||||
- [Store](architecture/store/store.md)
|
- [Store](architecture/store/store.md)
|
||||||
- [Store Path](architecture/store/path.md)
|
- [Store Object](architecture/store/store.md#store-object)
|
||||||
|
- [Reference](architecture/store/store.md#reference)
|
||||||
|
- [Operations](architecture/store/store.md#operations)
|
||||||
|
- [Closure](architecture/store/store.md#closure)
|
||||||
|
- [Files and Processes](architecture/store/store.md#files-and-processes)
|
||||||
|
- [Build system terminology](architecture/store/store.md#build-system-terminology)
|
||||||
|
- [Store Path](architecture/store/path.md)
|
||||||
- [Digest](architecture/store/path.md#digest)
|
- [Digest](architecture/store/path.md#digest)
|
||||||
- [Input Addressing](architecture/store/path.md#input-addressing)
|
- [Input Addressing](architecture/store/path.md#input-addressing)
|
||||||
- [Content Addressing](architecture/store/path.md#content-addressing)
|
- [Content Addressing](architecture/store/path.md#content-addressing)
|
||||||
|
|
|
@ -36,13 +36,13 @@ Nix makes no distinction if store objects are build inputs, build results, or bu
|
||||||
|
|
||||||
Store objects are [immutable][immutable-object]: once created, they do not change until they are deleted.
|
Store objects are [immutable][immutable-object]: once created, they do not change until they are deleted.
|
||||||
|
|
||||||
## Reference
|
## Reference {#reference}
|
||||||
|
|
||||||
A store object reference is an [opaque][opaque-data-type], [unique identifier][unique-identifier]:
|
A store object reference is an [opaque][opaque-data-type], [unique identifier][unique-identifier]:
|
||||||
The only way to obtain references is by adding or building store objects.
|
The only way to obtain references is by adding or building store objects.
|
||||||
A reference will always point to exactly one store object.
|
A reference will always point to exactly one store object.
|
||||||
|
|
||||||
## Operations
|
## Operations {#operations}
|
||||||
|
|
||||||
A Nix store can *add*, *retrieve*, and *delete* store objects.
|
A Nix store can *add*, *retrieve*, and *delete* store objects.
|
||||||
|
|
||||||
|
@ -178,7 +178,7 @@ Examples:
|
||||||
|
|
||||||
To make store objects accessible to processes, stores ultimately have to expose store objects through the file system.
|
To make store objects accessible to processes, stores ultimately have to expose store objects through the file system.
|
||||||
|
|
||||||
## A [Rosetta stone][rosetta-stone] for build system terminology
|
## A [Rosetta stone][rosetta-stone] for build system terminology {#build-system-terminology}
|
||||||
|
|
||||||
The Nix store's design is comparable to other build systems.
|
The Nix store's design is comparable to other build systems.
|
||||||
Usage of terms is, for historic reasons, not entirely consistent within the Nix ecosystem, and still subject to slow change.
|
Usage of terms is, for historic reasons, not entirely consistent within the Nix ecosystem, and still subject to slow change.
|
||||||
|
|
Loading…
Reference in a new issue