2c1ecf8e81
This is equivalent to running ‘nix-env -e '*'’ first, except that it happens in a single transaction. Thus, ‘nix-env -i pkgs...’ replaces the profile with the specified set of packages. The main motivation is to support declarative package management (similar to environment.systemPackages in NixOS). That is, if you have a specification ‘profile.nix’ like this: with import <nixpkgs> {}; [ thunderbird geeqie ... ] then after any change to ‘profile.nix’, you can run: $ nix-env -f profile.nix -ir to update the profile to match the specification. (Without the ‘-r’ flag, if you remove a package from ‘profile.nix’, it won't be removed from the actual profile.) Suggested by @zefhemel. |
||
---|---|---|
corepkgs | ||
doc | ||
misc | ||
perl | ||
scripts | ||
src | ||
tests | ||
.gitignore | ||
AUTHORS | ||
bootstrap.sh | ||
build.nix | ||
configure.ac | ||
COPYING | ||
dev-shell | ||
INSTALL | ||
Makefile.am | ||
nix.spec.in | ||
README | ||
release.nix | ||
substitute.mk | ||
version |
Nix is a purely functional package manager. For installation and usage instructions, please read the manual, which can be found in `docs/manual/manual.html', and additionally at the Nix website at <http://nixos.org/>. Acknowledgments This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.OpenSSL.org/).