forked from lix-project/lix
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). |
||
---|---|---|
.. | ||
lang | ||
add.sh | ||
build-hook.hook.sh | ||
build-hook.nix.in | ||
build-hook.sh | ||
check-refs.nix.in | ||
check-refs.sh | ||
common.sh.in | ||
dependencies.builder0.sh | ||
dependencies.builder1.sh | ||
dependencies.builder2.sh | ||
dependencies.nix.in | ||
dependencies.sh | ||
export.sh | ||
fallback.sh | ||
filter-source.nix.in | ||
filter-source.sh | ||
fixed.builder1.sh | ||
fixed.builder2.sh | ||
fixed.nix.in | ||
fixed.sh | ||
gc-concurrent.builder.sh | ||
gc-concurrent.nix.in | ||
gc-concurrent.sh | ||
gc-concurrent2.builder.sh | ||
gc-concurrent2.nix.in | ||
gc-runtime.nix.in | ||
gc-runtime.sh | ||
gc.sh | ||
hash-check.nix | ||
hash.sh | ||
init.sh | ||
install-package.sh | ||
lang.sh | ||
locking.builder.sh | ||
locking.nix.in | ||
locking.sh | ||
logging.sh | ||
Makefile.am | ||
misc.sh | ||
nix-build.sh | ||
nix-pull.sh | ||
nix-push.sh | ||
parallel.builder.sh | ||
parallel.nix.in | ||
parallel.sh | ||
referrers.sh | ||
remote-store.sh | ||
simple.builder.sh | ||
simple.nix.in | ||
simple.sh | ||
substituter.sh | ||
substituter2.sh | ||
substitutes.sh | ||
substitutes2.sh | ||
user-envs.builder.sh | ||
user-envs.nix.in | ||
user-envs.sh | ||
verify.sh |