2021-12-13 17:48:44 +02:00
|
|
|
# Release X.Y (202?-??-??)
|
2022-03-16 20:48:50 +02:00
|
|
|
|
|
|
|
|
* Various nix commands can now read expressions from stdin with `--file -`.
|
2022-03-22 22:54:49 +02:00
|
|
|
|
|
|
|
|
* `nix store make-content-addressable` has been renamed to `nix store
|
|
|
|
|
make-content-addressed`.
|
2022-03-23 00:31:48 +02:00
|
|
|
|
2022-03-25 15:04:18 +02:00
|
|
|
* New experimental builtin function `builtins.fetchClosure` that
|
|
|
|
|
copies a closure from a binary cache at evaluation time and rewrites
|
|
|
|
|
it to content-addressed form (if it isn't already). Like
|
2022-03-23 00:31:48 +02:00
|
|
|
`builtins.storePath`, this allows importing pre-built store paths;
|
|
|
|
|
the difference is that it doesn't require the user to configure
|
|
|
|
|
binary caches and trusted public keys.
|
2022-03-25 15:04:18 +02:00
|
|
|
|
|
|
|
|
This function is only available if you enable the experimental
|
|
|
|
|
feature `fetch-closure`.
|
2022-03-31 18:33:06 +03:00
|
|
|
|
|
|
|
|
* New experimental feature: *impure derivations*. These are
|
|
|
|
|
derivations that can produce a different result every time they're
|
|
|
|
|
built. Here is an example:
|
|
|
|
|
|
|
|
|
|
```nix
|
|
|
|
|
stdenv.mkDerivation {
|
|
|
|
|
name = "impure";
|
|
|
|
|
__impure = true; # marks this derivation as impure
|
|
|
|
|
buildCommand = "date > $out";
|
|
|
|
|
}
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Running `nix build` twice on this expression will build the
|
|
|
|
|
derivation twice, producing two different content-addressed store
|
|
|
|
|
paths. Like fixed-output derivations, impure derivations have access
|
|
|
|
|
to the network. Only fixed-output derivations and impure derivations
|
|
|
|
|
can depend on an impure derivation.
|
