diff options
| author | John Ericson <John.Ericson@Obsidian.Systems> | 2022-04-19 02:20:15 -0400 |
|---|---|---|
| committer | Valentin Gagarin <valentin.gagarin@tweag.io> | 2022-08-04 12:37:46 +0200 |
| commit | c86c1ec7e31c2725be20e4087845e96878134846 (patch) | |
| tree | 48fd6bd5589819495c5ab32d76d5ca0f9da8301f | |
| parent | 4e4bbd9e832e810b4e4cf33aced0ec0322cf55b6 (diff) | |
Make refernces sneak preview more concise
| -rw-r--r-- | doc/manual/src/design/store/objects.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/manual/src/design/store/objects.md b/doc/manual/src/design/store/objects.md index 0f3d2a499..e4f49a170 100644 --- a/doc/manual/src/design/store/objects.md +++ b/doc/manual/src/design/store/objects.md @@ -62,9 +62,8 @@ Store objects can refer to both other store objects and themselves. Self-reference may seem pointless, but tracking them is in fact useful. We can best explain why later after more concepts have been established. -References are normally calculated by scanning the rooted file system objects for store paths (which we describe in the next section) referring to store objects. -For now, it suffices to say that a store path is a string encoding of a reference to a store paths, and therefore it is something that we can search for in the contents of files, and thus in store objects by searching in all their files. -When we get to building in a future section, this process will be described in precise detail. +References are normally calculated so as to to record the presence of textual references in store object's file systems obejcts. +This process will be described precisely in the section on [building](./building.md), once more concepts are explained, as building is the primary path new store objects with non-trivial references are created. However, scanning for references is not mandatory. Store objects are allowed to have official references that *don't* correspond to store paths contained in their contents, |