nix/tests/functional/add.sh

source common.sh

path1=$(nix-store --add ./dummy)
echo $path1

path2=$(nix-store --add-fixed sha256 --recursive ./dummy)
echo $path2

if test "$path1" != "$path2"; then
    echo "nix-store --add and --add-fixed mismatch"
    exit 1
fi

path3=$(nix-store --add-fixed sha256 ./dummy)
echo $path3
test "$path1" != "$path3" || exit 1

path4=$(nix-store --add-fixed sha1 --recursive ./dummy)
echo $path4
test "$path1" != "$path4" || exit 1

hash1=$(nix-store -q --hash $path1)
echo $hash1

hash2=$(nix-hash --type sha256 --base32 ./dummy)
echo $hash2

test "$hash1" = "sha256:$hash2"

#### New style commands

clearStore

(
    path1=$(nix store add ./dummy)
    path2=$(nix store add --mode nar ./dummy)
    path3=$(nix store add-path ./dummy)
    [[ "$path1" == "$path2" ]]
    [[ "$path1" == "$path3" ]]
)
(
    path1=$(nix store add --mode flat ./dummy)
    path2=$(nix store add-file ./dummy)
    [[ "$path1" == "$path2" ]]
)
* Test `nix-store --add' and `nix-store -q --hash'. 2006-03-01 15:43:37 +00:00			`source common.sh`

* Refactoring: remove unnecessary variables from the tests. 2011-10-10 21:32:34 +00:00			`path1=$(nix-store --add ./dummy)`
* Unify the treatment of sources copied to the store, and recursive 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). 2008-12-03 15:06:30 +00:00			`echo $path1`
* Test `nix-store --add' and `nix-store -q --hash'. 2006-03-01 15:43:37 +00:00
* Refactoring: remove unnecessary variables from the tests. 2011-10-10 21:32:34 +00:00			`path2=$(nix-store --add-fixed sha256 --recursive ./dummy)`
* Unify the treatment of sources copied to the store, and recursive 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). 2008-12-03 15:06:30 +00:00			`echo $path2`
* Test `nix-store --add' and `nix-store -q --hash'. 2006-03-01 15:43:37 +00:00
* Unify the treatment of sources copied to the store, and recursive 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). 2008-12-03 15:06:30 +00:00			`if test "$path1" != "$path2"; then`
			`echo "nix-store --add and --add-fixed mismatch"`
			`exit 1`
tests/check.sh: Fix a race Fixes this random failure: error: hash mismatch in fixed-output derivation '/tmp/nix-shell.EUgAVU/nix-test/tests/check/store/sfps3l3c5n7dabpx34kigxnfhmrwk2h6-dummy.drv': specified: sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU= got: sha256-0qhPS4tlCTfsj3PNi+LHSt1akRumTfJ0WO2CKdqASiY= which happens because multiple tests were writing to ./dummy. 2021-07-07 08:48:47 +00:00			`fi`
* Test `nix-store --add' and `nix-store -q --hash'. 2006-03-01 15:43:37 +00:00
* Refactoring: remove unnecessary variables from the tests. 2011-10-10 21:32:34 +00:00			`path3=$(nix-store --add-fixed sha256 ./dummy)`
* Unify the treatment of sources copied to the store, and recursive 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). 2008-12-03 15:06:30 +00:00			`echo $path3`
			`test "$path1" != "$path3" \|\| exit 1`
* Test `nix-store --add' and `nix-store -q --hash'. 2006-03-01 15:43:37 +00:00
* Refactoring: remove unnecessary variables from the tests. 2011-10-10 21:32:34 +00:00			`path4=$(nix-store --add-fixed sha1 --recursive ./dummy)`
* Unify the treatment of sources copied to the store, and recursive 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). 2008-12-03 15:06:30 +00:00			`echo $path4`
			`test "$path1" != "$path4" \|\| exit 1`
* Test `nix-store --add' and `nix-store -q --hash'. 2006-03-01 15:43:37 +00:00
* Refactoring: remove unnecessary variables from the tests. 2011-10-10 21:32:34 +00:00			`hash1=$(nix-store -q --hash $path1)`
* Unify the treatment of sources copied to the store, and recursive 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). 2008-12-03 15:06:30 +00:00			`echo $hash1`

* Refactoring: remove unnecessary variables from the tests. 2011-10-10 21:32:34 +00:00			`hash2=$(nix-hash --type sha256 --base32 ./dummy)`
* Unify the treatment of sources copied to the store, and recursive 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). 2008-12-03 15:06:30 +00:00			`echo $hash2`

			`test "$hash1" = "sha256:$hash2"`
Add a new `nix store add` command Deprecate `nix store add-file` and `nix store add-path`, and replace them with a single `nix store add` command. 2023-11-15 08:23:26 +00:00
			`#### New style commands`

			`clearStore`

			`(`
			`path1=$(nix store add ./dummy)`
			`path2=$(nix store add --mode nar ./dummy)`
			`path3=$(nix store add-path ./dummy)`
			`[[ "$path1" == "$path2" ]]`
			`[[ "$path1" == "$path3" ]]`
			`)`
			`(`
			`path1=$(nix store add --mode flat ./dummy)`
			`path2=$(nix store add-file ./dummy)`
			`[[ "$path1" == "$path2" ]]`
			`)`