aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEelco Dolstra <edolstra@gmail.com>2018-02-03 10:04:29 +0100
committerEelco Dolstra <edolstra@gmail.com>2018-02-03 10:08:05 +0100
commit84722d67d2b09b5c28e1c2d9dd438ba592df2296 (patch)
tree81f9563b7bd1440209a7a706a8646a9ff0af9e71 /doc
parentde96daf54f3143753073314e0c0e23851c568633 (diff)
Remove nix-build --hash
Instead, if a fixed-output derivation produces has an incorrect output hash, we now unconditionally move the outputs to the path corresponding with the actual hash and register it as valid. Thus, after correcting the hash in the Nix expression (e.g. in a fetchurl call), the fixed-output derivation doesn't have to be built again. It would still be good to have a command for reporting the actual hash of a fixed-output derivation (instead of throwing an error), but "nix-build --hash" didn't do that.
Diffstat (limited to 'doc')
-rw-r--r--doc/manual/release-notes/rl-2.0.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/manual/release-notes/rl-2.0.xml b/doc/manual/release-notes/rl-2.0.xml
index 0d485c369..32cdb1d0c 100644
--- a/doc/manual/release-notes/rl-2.0.xml
+++ b/doc/manual/release-notes/rl-2.0.xml
@@ -99,11 +99,11 @@
</listitem>
<listitem>
- <para>New build mode <command>nix-build --hash</command> that
- builds a derivation, computes the hash of the output, and moves
- the output to the store path corresponding to what a fixed-output
- derivation with that hash would produce.
- (Add docs and examples; see d367b8e7875161e655deaa96bf8a5dd0bcf8229e)</para>
+ <para>If a fixed-output derivation produces a result with an
+ incorrect hash, the output path will be moved to the location
+ corresponding to the actual hash and registered as valid. Thus, a
+ subsequent build of the fixed-output derivation with the correct
+ hash is unnecessary.</para>
</listitem>
<listitem>