From 355a923e812f07cb6ab72776114e4d1ad2c7dacd Mon Sep 17 00:00:00 2001 From: oldshensheep Date: Tue, 18 Mar 2025 18:01:40 +0800 Subject: [PATCH] Improve the documentation of store path # Conflicts: # doc/manual/source/protocols/store-path.md --- doc/manual/source/protocols/store-path.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/manual/source/protocols/store-path.md b/doc/manual/source/protocols/store-path.md index ee7fb3a12..5be235501 100644 --- a/doc/manual/source/protocols/store-path.md +++ b/doc/manual/source/protocols/store-path.md @@ -7,7 +7,7 @@ The format of this specification is close to [Extended Backus–Naur form](https Regular users do *not* need to know this information --- store paths can be treated as black boxes computed from the properties of the store objects they refer to. But for those interested in exactly how Nix works, e.g. if they are reimplementing it, this information can be useful. -[store path](@docroot@/store/store-path.md) +[store path]: @docroot@/store/store-path.md ## Store path proper @@ -30,7 +30,7 @@ the end, while base-16 processes in from the beginning. ## Fingerprint - ```ebnf - fingerprint = type ":" sha256 ":" inner-digest ":" store ":" name + fingerprint = type ":sha256:" inner-digest ":" store ":" name ``` Note that it includes the location of the store as well as the name to make sure that changes to either of those are reflected in the hash