mirror of
https://github.com/NixOS/nix
synced 2025-07-07 14:21:48 +02:00
<replaceable> -> <emphasis>
Pandoc doesn't know <replaceable> so let's force it to be rendered as italics.
This commit is contained in:
parent
ee05108472
commit
802150f987
76 changed files with 1029 additions and 1020 deletions
|
@ -34,7 +34,7 @@
|
|||
|
||||
- `nix-env -i
|
||||
pkgname` will now install the highest available version of
|
||||
pkgname, rather than installing all available versions (which
|
||||
*pkgname*, rather than installing all available versions (which
|
||||
would probably give collisions) (`NIX-31`).
|
||||
|
||||
- `nix-env (-i|-u) --dry-run` now shows exactly which missing
|
||||
|
|
|
@ -41,10 +41,10 @@
|
|||
|
||||
- The garbage collector has a number of new options to allow only some
|
||||
of the garbage to be deleted. The option `--max-freed N` tells the
|
||||
collector to stop after at least N bytes have been deleted. The
|
||||
collector to stop after at least *N* bytes have been deleted. The
|
||||
option `--max-links
|
||||
N` tells it to stop after the link count on `/nix/store` has dropped
|
||||
below N. This is useful for very large Nix stores on filesystems
|
||||
below *N*. This is useful for very large Nix stores on filesystems
|
||||
with a 32000 subdirectories limit (like `ext3`). The option
|
||||
`--use-atime` causes store paths to be deleted in order of ascending
|
||||
last access time. This allows non-recently used stuff to be deleted.
|
||||
|
|
|
@ -51,5 +51,5 @@ This is primarily a bug fix release. It has some new features:
|
|||
option is used.
|
||||
|
||||
- The scoping rules for `inherit
|
||||
(e) ...` in recursive attribute sets have changed. The expression e
|
||||
can now refer to the attributes defined in the containing set.
|
||||
(e) ...` in recursive attribute sets have changed. The expression
|
||||
*e* can now refer to the attributes defined in the containing set.
|
||||
|
|
|
@ -15,7 +15,7 @@ This release has the following improvements:
|
|||
`--cores
|
||||
N` as well as a configuration setting `build-cores =
|
||||
N` that causes the environment variable `NIX_BUILD_CORES` to be set
|
||||
to N when the builder is invoked. The builder can use this at its
|
||||
to *N* when the builder is invoked. The builder can use this at its
|
||||
discretion to perform a parallel build, e.g., by calling `make -j
|
||||
N`. In Nixpkgs, this can be enabled on a per-package basis by
|
||||
setting the derivation attribute `enableParallelBuilding` to `true`.
|
||||
|
|
|
@ -49,8 +49,8 @@
|
|||
|
||||
- New language construct: `with
|
||||
E1;
|
||||
E2` brings all attributes defined in the attribute set E1 in
|
||||
scope in E2.
|
||||
E2` brings all attributes defined in the attribute set *E1* in
|
||||
scope in *E2*.
|
||||
|
||||
- Added a `map` function.
|
||||
|
||||
|
|
|
@ -35,7 +35,7 @@ features:
|
|||
derivations, and in `builtins.hashString`.
|
||||
|
||||
- The new flag `--option build-repeat
|
||||
N` will cause every build to be executed N+1 times. If the build
|
||||
N` will cause every build to be executed *N*+1 times. If the build
|
||||
output differs between any round, the build is rejected, and the
|
||||
output paths are not registered as valid. This is primarily useful
|
||||
to verify build determinism. (We already had a `--check` option to
|
||||
|
|
|
@ -10,7 +10,7 @@ There are also the following improvements:
|
|||
|
||||
- New built-in function: `builtins.hashString`.
|
||||
|
||||
- Build logs are now stored in `/nix/var/log/nix/drvs/XX/`, where XX
|
||||
- Build logs are now stored in `/nix/var/log/nix/drvs/XX/`, where *XX*
|
||||
is the first two characters of the derivation. This is useful on
|
||||
machines that keep a lot of build logs (such as Hydra servers).
|
||||
|
||||
|
|
|
@ -6,8 +6,8 @@ This is primarily a bug fix release. Changes of interest are:
|
|||
strings, such as `"${/foo}/bar"`. This release reverts to the Nix
|
||||
1.5.3 behaviour.
|
||||
|
||||
- Previously, Nix optimised expressions such as `"${expr}"` to expr.
|
||||
Thus it neither checked whether expr could be coerced to a string,
|
||||
- Previously, Nix optimised expressions such as `"${expr}"` to *expr*.
|
||||
Thus it neither checked whether *expr* could be coerced to a string,
|
||||
nor applied such coercions. This meant that `"${123}"` evaluatued to
|
||||
`123`, and `"${./foo}"` evaluated to `./foo` (even though `"${./foo}
|
||||
"` evaluates to `"/nix/store/hash-foo "`). Nix now checks the type
|
||||
|
|
|
@ -89,10 +89,10 @@ features:
|
|||
specifier. For example, `nix-store --gc --max-freed
|
||||
1G` will free up to 1 gigabyte of disk space.
|
||||
|
||||
- `nix-collect-garbage` has a new flag `--delete-older-than` N`d`,
|
||||
which deletes all user environment generations older than N days.
|
||||
- `nix-collect-garbage` has a new flag `--delete-older-than` *N*`d`,
|
||||
which deletes all user environment generations older than *N* days.
|
||||
Likewise, `nix-env
|
||||
--delete-generations` accepts a N`d` age limit.
|
||||
--delete-generations` accepts a *N*`d` age limit.
|
||||
|
||||
- Nix now heuristically detects whether a build failure was due to a
|
||||
disk-full condition. In that case, the build is not flagged as
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue