about summary refs log tree commit diff
path: root/doc/manual/release-notes.xml
AgeCommit message (Collapse)AuthorFilesLines
2012-06-23 Update release notesEelco Dolstra1-1/+15
2012-05-29 Add option ‘build-keep-log’ to enable/disable writing of build logsEelco Dolstra1-0/+20
Fixes #26.
2012-05-11 Set release dateEelco Dolstra1-1/+1
2012-05-09 Update the release notesEelco Dolstra1-12/+82
2012-01-17 * Added a command ‘nix-store --print-env $drvpath’ that prints out theEelco Dolstra1-0/+4
environment of the given derivation in a format that can be sourced by the shell, e.g. $ eval "$(nix-store --print-env $(nix-instantiate /etc/nixos/nixpkgs -A pkg))" $ NIX_BUILD_TOP=/tmp $ source $stdenv/setup This is especially useful to reproduce the environment used to build a package outside of its builder for development purposes. TODO: add a nix-build option to do the above and fetch the dependencies of the derivation as well.
2011-09-06 * Added a command ‘nix-store --verify-paths PATHS’ to check whetherEelco Dolstra1-0/+4
the contents of any of the given store paths have been modified. E.g. $ nix-store --verify-path $(nix-store -qR /var/run/current-system) path `/nix/store/m2smyiwbxidlprfxfz4rjlvz2c3mg58y-etc' was modified! expected hash `fc87e271c5fdf179b47939b08ad13440493805584b35e3014109d04d8436e7b8', got `20f1a47281b3c0cbe299ce47ad5ca7340b20ab34246426915fce0ee9116483aa' All paths are checked; the exit code is 1 if any path has been modified, 0 otherwise.
2011-08-06 * Add a Nix expression search path feature. Paths between angleEelco Dolstra1-0/+4
brackets, e.g. import <nixpkgs/pkgs/lib> are resolved by looking them up relative to the elements listed in the search path. This allows us to get rid of hacks like import "${builtins.getEnv "NIXPKGS_ALL"}/pkgs/lib" The search path can be specified through the ‘-I’ command-line flag and through the colon-separated ‘NIX_PATH’ environment variable, e.g., $ nix-build -I /etc/nixos ... If a file is not found in the search path, an error message is lazily thrown.
2011-07-13 * Allow a default value in attribute selection by writingEelco Dolstra1-0/+4
x.y.z or default (as originally proposed in https://mail.cs.uu.nl/pipermail/nix-dev/2009-September/002989.html). For instance, an expression like stdenv.lib.attrByPath ["features" "ckSched"] false args can now be written as args.features.ckSched or false
2011-06-30 Add support for the `build-timeout' and `--timeout' options.Ludovic Courtès1-0/+10
2010-10-29 * Document Boehm GC support.Eelco Dolstra1-0/+21
2010-08-17 * Document --cores in the manual.Eelco Dolstra1-3/+3
2010-08-16 * Nix 0.16 release notes.Eelco Dolstra1-0/+53
2010-03-17 (no commit message)Eelco Dolstra1-1/+1
2010-03-16 * Release notes for Nix 0.15.Eelco Dolstra1-0/+12
2010-02-04 (no commit message)Eelco Dolstra1-1/+1
2010-02-03 * Updated the release notes.Eelco Dolstra1-1/+5
2009-12-09 * Release notes.Eelco Dolstra1-0/+40
2009-11-05 * Various updates.Eelco Dolstra1-1/+1
2009-11-04 * Manual updates.Eelco Dolstra1-2/+20
2009-09-25 (no commit message)Eelco Dolstra1-1/+1
2009-05-26 (no commit message)Eelco Dolstra1-0/+27
2009-04-14 * Release notes.Eelco Dolstra1-0/+60
2008-11-20 (no commit message)Eelco Dolstra1-1/+2
2008-11-19 * Updated the manual.Eelco Dolstra1-1/+1
2008-11-19 * Remove references to Berkeley DB, including most of theEelco Dolstra1-2/+2
troubleshooting section. W00t.
2008-11-19 * Release notes.Eelco Dolstra1-18/+138
2008-11-18 * Get rid of nix-pack-closure / nix-unpack-closure, they're redundant.Eelco Dolstra1-0/+7
2008-08-05 * Moved some stuff to the Nixpkgs manual.Eelco Dolstra1-0/+22
* Updated the release notes.
2008-07-11 * Generalised the dependencyClosure primop to builtins.genericClosure,Eelco Dolstra1-2/+7
which is hopefully more useful. * New primops: length, mul, div.
2008-07-01 * Export the nix-env derivation name parsing and version comparisonEelco Dolstra1-0/+6
logic through the `parseDrvName' and `compareVersions' primops. This will allow expressions to easily check whether some dependency is a specific needed version or falls in some version range. See tests/lang/eval-okay-versions.nix for examples.
2008-01-29 * nix-store --dump-db / --load-db to dump/load the Nix DB.Eelco Dolstra1-0/+13
* nix-store --register-validity: option to supply the content hash of each path. * Removed compatibility with Nix <= 0.7 stores.
2007-12-31 (no commit message)Eelco Dolstra1-4/+5
2007-12-31 (no commit message)Eelco Dolstra1-89/+89
2007-12-31 (no commit message)Eelco Dolstra1-9/+8
2007-12-31 * More release notes.Eelco Dolstra1-0/+44
2007-12-30 * Documented indented string literals.Eelco Dolstra1-39/+121
* Release notes.
2007-11-30 * Added a new kind of multi-line string literal delimited by twoEelco Dolstra1-0/+4
single quotes. Example (from NixOS): job = '' start on network-interfaces start script rm -f /var/run/opengl-driver ${if videoDriver == "nvidia" then "ln -sf ${nvidiaDrivers} /var/run/opengl-driver" else if cfg.driSupport then "ln -sf ${mesa} /var/run/opengl-driver" else "" } rm -f /var/log/slim.log end script ''; This style has two big advantages: - \, ' and " aren't special, only '' and ${. So you get a lot less escaping in shell scripts / configuration files in Nixpkgs/NixOS. The delimiter '' is rare in scripts (and can usually be written as ""). ${ is also fairly rare. Other delimiters such as <<...>>, {{...}} and <|...|> were also considered but this one appears to have the fewest drawbacks (thanks Martin). - Indentation is intelligently stripped so that multi-line strings can follow the nesting structure of the containing Nix expression. E.g. in the example above 6 spaces are stripped from the start of each line. This prevents unnecessary indentation in generated files (which sometimes even breaks things). See tests/lang/eval-okay-ind-string.nix for some examples.
2007-11-01 * Documented some of the more obscure derivation attributes (includingEelco Dolstra1-7/+16
fixed-output derivations).
2007-10-29 * Make the `--prebuilt-only' / `-b' option work not just for queriesEelco Dolstra1-1/+2
but installations/upgrades as well. So `nix-env -ub \*' will upgrade only those packages for which a substitute is available (or to be precise, it will upgrade each package to the highest version for which a substitute is available).
2007-10-27 * Delete the chroot directory automatically.Eelco Dolstra1-0/+3
* Removed some debug messages.
2007-09-19 * Manpage for nix-copy-closure.Eelco Dolstra1-5/+22
2007-05-16 (no commit message)Eelco Dolstra1-1/+3
2007-05-01 * nix-env -i: instead of breaking package ties by version, break themEelco Dolstra1-0/+6
by priority and version install. That is, if there are multiple packages with the same name, then pick the package with the highest priority, and only use the version if there are multiple packages with the same priority. This makes it possible to mark specific versions/variant in Nixpkgs more or less desirable than others. A typical example would be a beta version of some package (e.g., "gcc-4.2.0rc1") which should not be installed even though it is the highest version, except when it is explicitly selected (e.g., "nix-env -i gcc-4.2.0rc1"). * Idem for nix-env -u, only the semantics are a bit trickier since we also need to take into account the priority of the currently installed package (we never upgrade to a lower priority, unless --always is given).
2007-05-01 * `nix-env -q --xml --meta' to show all meta attributes.Eelco Dolstra1-2/+2
2007-04-27 * Package flag "keep" that prevents a package from being removed fromEelco Dolstra1-2/+2
a user environment by an install or upgrade action. This is particularly useful if you have a version installed that you don't want to upgrade (e.g., because the newer versions are broken). Example: $ nix-env -u zapping --dry-run (dry run; not doing anything) upgrading `zapping-0.9.6' to `zapping-0.10cvs6' $ nix-env --set-flag keep true zapping $ nix-env -u zapping --dry-run (dry run; not doing anything) However, "-e" will still uninstall the package. (Maybe we should require the keep flag to be explicitly set to false before it can be uninstalled.)
2007-04-27 * Package conflict resolution through priority levels. If there is aEelco Dolstra1-1/+3
user environment collission between two packages due to overlapping file names, then a package with a higher priority will overwrite the symlinks of a package with a lower priority. E.g., $ nix-env --set-flag priority 5 gcc $ nix-env --set-flag priority 10 binutils gives gcc a higher priority than binutils (higher number = lower priority).
2007-04-26 * nix-env -q now has a flag --prebuilt-only (-b<) that causes nix-envEelco Dolstra1-0/+9
to show only those derivations whose output is already in the Nix store or that can be substituted (i.e., downloaded from somewhere). In other words, it shows the packages that can be installed “quickly”, i.e., don’t need to be built from source.
2007-03-26 * `nix-copy-closure --from': copy from a remote machine instead of toEelco Dolstra1-0/+5
a remote machine.
2007-02-02 * nix-env now maintains meta info (from the `meta' derivationEelco Dolstra1-0/+16
attribute) about installed packages in user environments. Thus, an operation like `nix-env -q --description' shows useful information not only on available packages but also on installed packages. * nix-env now passes the entire manifest as an argument to the Nix expression of the user environment builder (not just a list of paths), so that in particular the user environment builder has access to the meta attributes. * New operation `--set-flag' in nix-env to change meta info of installed packages. This will be useful to pass per-package policies to the user environment builder (e.g., how to resolve collision or whether to disable a package (NIX-80)) or upgrade policies in nix-env (e.g., that a package should be "masked", that is, left untouched by upgrade actions). Example: $ nix-env --set-flag enabled false ghc-6.4
2007-01-29 New primitives:Eelco Dolstra1-1/+4
* `sub' to subtract two numbers. * `stringLength' to get the length of a string. * `substring' to get a substring of a string. These should be enough to allow most string operations to be expressed.