mirror of
https://github.com/privatevoid-net/nix-super.git
synced 2024-11-14 02:06:16 +02:00
64519cfd65
SHA-256 outputs of fixed-output derivations. I.e. they now produce
the same store path:
$ nix-store --add x
/nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x
$ nix-store --add-fixed --recursive sha256 x
/nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x
the latter being the same as the path that a derivation
derivation {
name = "x";
outputHashAlgo = "sha256";
outputHashMode = "recursive";
outputHash = "...";
...
};
produces.
This does change the output path for such fixed-output derivations.
Fortunately they are quite rare. The most common use is fetchsvn
calls with SHA-256 hashes. (There are a handful of those is
Nixpkgs, mostly unstable development packages.)
* Documented the computation of store paths (in store-api.cc).
28 lines
584 B
Bash
28 lines
584 B
Bash
source common.sh
|
|
|
|
path1=$($nixstore --add ./dummy)
|
|
echo $path1
|
|
|
|
path2=$($nixstore --add-fixed sha256 --recursive ./dummy)
|
|
echo $path2
|
|
|
|
if test "$path1" != "$path2"; then
|
|
echo "nix-store --add and --add-fixed mismatch"
|
|
exit 1
|
|
fi
|
|
|
|
path3=$($nixstore --add-fixed sha256 ./dummy)
|
|
echo $path3
|
|
test "$path1" != "$path3" || exit 1
|
|
|
|
path4=$($nixstore --add-fixed sha1 --recursive ./dummy)
|
|
echo $path4
|
|
test "$path1" != "$path4" || exit 1
|
|
|
|
hash1=$($nixstore -q --hash $path1)
|
|
echo $hash1
|
|
|
|
hash2=$($nixhash --type sha256 --base32 ./dummy)
|
|
echo $hash2
|
|
|
|
test "$hash1" = "sha256:$hash2"
|