.\" -*- mode: troff; coding: utf-8 -*-
.TH "nix-env \(eninstall" "1" ""
.SH
Name
.LP
\fCnix-env --install\fR - add packages to user environment
.SH
Synopsis
.LP
\fCnix-env\fR {\fC--install\fR | \fC-i\fR} \fIargs…\fR
[{\fC--prebuilt-only\fR | \fC-b\fR}]
[{\fC--attr\fR | \fC-A\fR}]
[\fC--from-expression\fR] [\fC-E\fR]
[\fC--from-profile\fR \fIpath\fR]
[\fC--preserve-installed\fR | \fC-P\fR]
[\fC--remove-all\fR | \fC-r\fR]
.SH
Description
.LP
The install operation creates a new user environment.
It is based on the current generation of the active \fBprofile\fR, to which a set of \fBstore paths\fR described by \fIargs\fR is added.
.PP
The arguments \fIargs\fR map to store paths in a number of possible ways:
.IP "\(bu" 3
By default, \fIargs\fR is a set of [derivation] names denoting derivations in the [default Nix expression].
These are [realised], and the resulting output paths are installed.
Currently installed derivations with a name equal to the name of a derivation being added are removed unless the option \fC--preserve-installed\fR is specified.
.IP
[derivation]: @docroot@/glossary.md#gloss-derivation
[default Nix expression]: @docroot@/command-ref/files/default-nix-expression.md
[realised]: @docroot@/glossary.md#gloss-realise
.IP
If there are multiple derivations matching a name in \fIargs\fR that
have the same name (e.g., \fCgcc-3.3.6\fR and \fCgcc-4.1.1\fR), then the
derivation with the highest \fIpriority\fR is used. A derivation can
define a priority by declaring the \fCmeta.priority\fR attribute. This
attribute should be a number, with a higher value denoting a lower
priority. The default priority is \fC5\fR.
.IP
If there are multiple matching derivations with the same priority,
then the derivation with the highest version will be installed.
.IP
You can force the installation of multiple derivations with the same
name by being specific about the versions. For instance, \fCnix-env --install
gcc-3.3.6 gcc-4.1.1\fR will install both version of GCC (and will
probably cause a user environment conflict!).
.IP "\(bu" 3
If \fB\fC--attr\fR\fR / \fC-A\fR is specified, the arguments are \fIattribute paths\fR that select attributes from the [default Nix expression].
This is faster than using derivation names and unambiguous.
Show the attribute paths of available packages with \fB\fCnix-env --query\fR\fR:
.LP
.EX
nix-env --query --available --attr-path\(ga
.EE
.IP "\(bu" 3
If \fC--from-profile\fR \fIpath\fR is given, \fIargs\fR is a set of names
denoting installed \fBstore paths\fR in the profile \fIpath\fR. This is an
easy way to copy user environment elements from one profile to
another.
.IP "\(bu" 3
If \fC--from-expression\fR is given, \fIargs\fR are \fBNix language functions\fR that are called with the [default Nix expression] as their single argument.
The derivations returned by those function calls are installed.
This allows derivations to be specified in an unambiguous way, which is necessary if there are multiple derivations with the same name.
.IP "\(bu" 3
If \fIargs\fR are \fBstore derivations\fR, then these are [realised], and the resulting output paths are installed.
.IP "\(bu" 3
If \fIargs\fR are \fBstore paths\fR that are not store derivations, then these are [realised] and installed.
.IP "\(bu" 3
By default all \fBoutputs\fR are installed for each [derivation].
This can be overridden by adding a \fCmeta.outputsToInstall\fR attribute on the derivation listing a subset of the output names.
.IP
Example:
.IP
The file \fCexample.nix\fR defines a derivation with two outputs \fCfoo\fR and \fCbar\fR, each containing a file.
.LP
.EX
# example.nix
let
  pkgs = import <nixpkgs> {};
  command = ''
    ${pkgs.coreutils}/bin/mkdir -p $foo $bar
    echo foo > $foo/foo-file
    echo bar > $bar/bar-file
  '';
in
derivation {
  name = \(dqexample\(dq;
  builder = \(dq${pkgs.bash}/bin/bash\(dq;
  args = [ \(dq-c\(dq command ];
  outputs = [ \(dqfoo\(dq \(dqbar\(dq ];
  system = builtins.currentSystem;
}
.EE
.IP
Installing from this Nix expression will make files from both outputs appear in the current profile.
.LP
.EX
$ nix-env --install --file example.nix
installing 'example'
$ ls \(ti/.nix-profile
foo-file
bar-file
manifest.nix
.EE
.IP
Adding \fCmeta.outputsToInstall\fR to that derivation will make \fCnix-env\fR only install files from the specified outputs.
.LP
.EX
# example-outputs.nix
import ./example.nix // { meta.outputsToInstall = [ \(dqbar\(dq ]; }
.EE
.LP
.EX
$ nix-env --install --file example-outputs.nix
installing 'example'
$ ls \(ti/.nix-profile
bar-file
manifest.nix
.EE
.SH
Options
.IP "\(bu" 3
\fC--prebuilt-only\fR / \fC-b\fR
.IP
Use only derivations for which a substitute is registered, i.e.,
there is a pre-built binary available that can be downloaded in lieu
of building the derivation. Thus, no packages will be built from
source.
.IP "\(bu" 3
\fC--preserve-installed\fR / \fC-P\fR
.IP
Do not remove derivations with a name matching one of the
derivations being installed. Usually, trying to have two versions of
the same package installed in the same generation of a profile will
lead to an error in building the generation, due to file name
clashes between the two versions. However, this is not the case for
all packages.
.IP "\(bu" 3
\fC--remove-all\fR / \fC-r\fR
.IP
Remove all previously installed packages first. This is equivalent
to running \fCnix-env --uninstall '.*'\fR first, except that everything happens
in a single transaction.
.SH
Options
.LP
The following options are allowed for all \fCnix-env\fR operations, but may not always have an effect.
.IP "\(bu" 3
\fC--file\fR / \fC-f\fR \fIpath\fR
.br
Specifies the Nix expression (designated below as the \fIactive Nix
expression\fR) used by the \fC--install\fR, \fC--upgrade\fR, and \fC--query
--available\fR operations to obtain derivations. The default is
\fC\(ti/.nix-defexpr\fR.
.IP
If the argument starts with \fChttp://\fR or \fChttps://\fR, it is
interpreted as the URL of a tarball that will be downloaded and
unpacked to a temporary location. The tarball must include a single
top-level directory containing at least a file named \fCdefault.nix\fR.
.IP "\(bu" 3
\fC--profile\fR / \fC-p\fR \fIpath\fR
.br
Specifies the profile to be used by those operations that operate on
a profile (designated below as the \fIactive profile\fR). A profile is a
sequence of user environments called \fIgenerations\fR, one of which is
the \fIcurrent generation\fR.
.IP "\(bu" 3
\fC--dry-run\fR
.br
For the \fC--install\fR, \fC--upgrade\fR, \fC--uninstall\fR,
\fC--switch-generation\fR, \fC--delete-generations\fR and \fC--rollback\fR
operations, this flag will cause \fCnix-env\fR to print what \fIwould\fR be
done if this flag had not been specified, without actually doing it.
.IP
\fC--dry-run\fR also prints out which paths will be
\fBsubstituted\fR (i.e., downloaded) and which paths
will be built from source (because no substitute is available).
.IP "\(bu" 3
\fC--system-filter\fR \fIsystem\fR
.br
By default, operations such as \fC--query
--available\fR show derivations matching any platform. This option
allows you to use derivations for the specified platform \fIsystem\fR.
.SH
Common Options
.LP
Most Nix commands accept the following command-line options:
.IP "\(bu" 3
\fB\fC--help\fR\fR
.IP
Prints out a summary of the command syntax and exits.
.IP "\(bu" 3
\fB\fC--version\fR\fR
.IP
Prints out the Nix version number on standard output and exits.
.IP "\(bu" 3
\fB\fC--verbose\fR\fR / \fC-v\fR
.IP
Increases the level of verbosity of diagnostic messages printed on standard error.
For each Nix operation, the information printed on standard output is well-defined;
any diagnostic information is printed on standard error, never on standard output.
.IP
This option may be specified repeatedly.
Currently, the following verbosity levels exist:
.RS
.IP "\(bu" 3
\fC0\fR “Errors only”
.RE
.IP
Only print messages explaining why the Nix invocation failed.
.RS
.IP "\(bu" 3
\fC1\fR “Informational”
.RE
.IP
Print \fIuseful\fR messages about what Nix is doing.
This is the default.
.RS
.IP "\(bu" 3
\fC2\fR “Talkative”
.RE
.IP
Print more informational messages.
.RS
.IP "\(bu" 3
\fC3\fR “Chatty”
.RE
.IP
Print even more informational messages.
.RS
.IP "\(bu" 3
\fC4\fR “Debug”
.RE
.IP
Print debug information.
.RS
.IP "\(bu" 3
\fC5\fR “Vomit”
.RE
.IP
Print vast amounts of debug information.
.IP "\(bu" 3
\fB\fC--quiet\fR\fR
.IP
Decreases the level of verbosity of diagnostic messages printed on standard error.
This is the inverse option to \fC-v\fR / \fC--verbose\fR.
.IP
This option may be specified repeatedly.
See the previous verbosity levels list.
.IP "\(bu" 3
\fB\fC--log-format\fR\fR \fIformat\fR
.IP
This option can be used to change the output of the log format, with \fIformat\fR being one of:
.RS
.IP "\(bu" 3
\fCraw\fR
.RE
.IP
This is the raw format, as outputted by nix-build.
.RS
.IP "\(bu" 3
\fCinternal-json\fR
.RE
.IP
Outputs the logs in a structured manner.
.RS
.IP
\fBWarning\fR
.IP
While the schema itself is relatively stable, the format of
the error-messages (namely of the \fCmsg\fR-field) can change
between releases.
.RE
.RS
.IP "\(bu" 3
\fCbar\fR
.RE
.IP
Only display a progress bar during the builds.
.RS
.IP "\(bu" 3
\fCbar-with-logs\fR
.RE
.IP
Display the raw logs, with the progress bar at the bottom.
.IP "\(bu" 3
\fB\fC--no-build-output\fR\fR / \fC-Q\fR
.IP
By default, output written by builders to standard output and standard error is echoed to the Nix command\(cqs standard error.
This option suppresses this behaviour.
Note that the builder\(cqs standard output and error are always written to a log file in \fCprefix/nix/var/log/nix\fR.
.IP "\(bu" 3
\fB\fC--max-jobs\fR\fR / \fC-j\fR \fInumber\fR
.IP
Sets the maximum number of build jobs that Nix will perform in parallel to the specified number.
Specify \fCauto\fR to use the number of CPUs in the system.
The default is specified by the \fCmax-jobs\fR configuration setting, which itself defaults to \fC1\fR.
A higher value is useful on SMP systems or to exploit I/O latency.
.IP
Setting it to \fC0\fR disallows building on the local machine, which is useful when you want builds to happen only on remote builders.
.IP "\(bu" 3
\fB\fC--cores\fR\fR
.IP
Sets the value of the \fCNIX_BUILD_CORES\fR environment variable in the invocation of builders.
Builders can use this variable at their discretion to control the maximum amount of parallelism.
For instance, in Nixpkgs, if the derivation attribute \fCenableParallelBuilding\fR is set to \fCtrue\fR, the builder passes the \fC-jN\fR flag to GNU Make.
It defaults to the value of the \fCcores\fR configuration setting, if set, or \fC1\fR otherwise.
The value \fC0\fR means that the builder should use all available CPU cores in the system.
.IP "\(bu" 3
\fB\fC--max-silent-time\fR\fR
.IP
Sets the maximum number of seconds that a builder can go without producing any data on standard output or standard error.
The default is specified by the \fCmax-silent-time\fR configuration setting.
\fC0\fR means no time-out.
.IP "\(bu" 3
\fB\fC--timeout\fR\fR
.IP
Sets the maximum number of seconds that a builder can run.
The default is specified by the \fCtimeout\fR configuration setting.
\fC0\fR means no timeout.
.IP "\(bu" 3
\fB\fC--keep-going\fR\fR / \fC-k\fR
.IP
Keep going in case of failed builds, to the greatest extent possible.
That is, if building an input of some derivation fails, Nix will still build the other inputs, but not the derivation itself.
Without this option, Nix stops if any build fails (except for builds of substitutes), possibly killing builds in progress (in case of parallel or distributed builds).
.IP "\(bu" 3
\fB\fC--keep-failed\fR\fR / \fC-K\fR
.IP
Specifies that in case of a build failure, the temporary directory (usually in \fC/tmp\fR) in which the build takes place should not be deleted.
The path of the build directory is printed as an informational message.
.IP "\(bu" 3
\fB\fC--fallback\fR\fR
.IP
Whenever Nix attempts to build a derivation for which substitutes are known for each output path, but realising the output paths through the substitutes fails, fall back on building the derivation.
.IP
The most common scenario in which this is useful is when we have registered substitutes in order to perform binary distribution from, say, a network repository.
If the repository is down, the realisation of the derivation will fail.
When this option is specified, Nix will build the derivation instead.
Thus, installation from binaries falls back on installation from source.
This option is not the default since it is generally not desirable for a transient failure in obtaining the substitutes to lead to a full build from source (with the related consumption of resources).
.IP "\(bu" 3
\fB\fC--readonly-mode\fR\fR
.IP
When this option is used, no attempt is made to open the Nix database.
Most Nix operations do need database access, so those operations will fail.
.IP "\(bu" 3
\fB\fC--arg\fR\fR \fIname\fR \fIvalue\fR
.IP
This option is accepted by \fCnix-env\fR, \fCnix-instantiate\fR, \fCnix-shell\fR and \fCnix-build\fR.
When evaluating Nix expressions, the expression evaluator will automatically try to call functions that it encounters.
It can automatically call functions for which every argument has a \fBdefault value\fR (e.g., \fC{ argName ?  defaultValue }: ...\fR).
.IP
With \fC--arg\fR, you can also call functions that have arguments without a default value (or override a default value).
That is, if the evaluator encounters a function with an argument named \fIname\fR, it will call it with value \fIvalue\fR.
.IP
For instance, the top-level \fCdefault.nix\fR in Nixpkgs is actually a function:
.LP
.EX
{ # The system (e.g., \(gai686-linux') for which to build the packages.
system ? builtins.currentSystem
\&...
}: ...
.EE
.IP
So if you call this Nix expression (e.g., when you do \fCnix-env --install --attr pkgname\fR), the function will be called automatically using the value \fB\fCbuiltins.currentSystem\fR\fR for the \fCsystem\fR argument.
You can override this using \fC--arg\fR, e.g., \fCnix-env --install --attr pkgname --arg system \e\(dqi686-freebsd\e\(dq\fR.
(Note that since the argument is a Nix string literal, you have to escape the quotes.)
.IP "\(bu" 3
\fB\fC--argstr\fR\fR \fIname\fR \fIvalue\fR
.IP
This option is like \fC--arg\fR, only the value is not a Nix expression but a string.
So instead of \fC--arg system \e\(dqi686-linux\e\(dq\fR (the outer quotes are to keep the shell happy) you can say \fC--argstr system i686-linux\fR.
.IP "\(bu" 3
\fB\fC--attr\fR\fR / \fC-A\fR \fIattrPath\fR
.IP
Select an attribute from the top-level Nix expression being evaluated.
(\fCnix-env\fR, \fCnix-instantiate\fR, \fCnix-build\fR and \fCnix-shell\fR only.)
The \fIattribute path\fR \fIattrPath\fR is a sequence of attribute names separated by dots.
For instance, given a top-level Nix expression \fIe\fR, the attribute path \fCxorg.xorgserver\fR would cause the expression \fCe.xorg.xorgserver\fR to be used.
See \fB\fCnix-env --install\fR\fR for some concrete examples.
.IP
In addition to attribute names, you can also specify array indices.
For instance, the attribute path \fCfoo.3.bar\fR selects the \fCbar\fR
attribute of the fourth element of the array in the \fCfoo\fR attribute
of the top-level expression.
.IP "\(bu" 3
\fB\fC--expr\fR\fR / \fC-E\fR
.IP
Interpret the command line arguments as a list of Nix expressions to be parsed and evaluated, rather than as a list of file names of Nix expressions.
(\fCnix-instantiate\fR, \fCnix-build\fR and \fCnix-shell\fR only.)
.IP
For \fCnix-shell\fR, this option is commonly used to give you a shell in which you can build the packages returned by the expression.
If you want to get a shell which contain the \fIbuilt\fR packages ready for use, give your expression to the \fCnix-shell --packages\fR convenience flag instead.
.IP "\(bu" 3
\fB\fC-I\fR\fR \fIpath\fR
.IP
Add an entry to the \fBNix expression search path\fR.
This option may be given multiple times.
Paths added through \fC-I\fR take precedence over \fB\fCNIX_PATH\fR\fR.
.IP "\(bu" 3
\fB\fC--option\fR\fR \fIname\fR \fIvalue\fR
.IP
Set the Nix configuration option \fIname\fR to \fIvalue\fR.
This overrides settings in the Nix configuration file (see nix.conf5).
.IP "\(bu" 3
\fB\fC--repair\fR\fR
.IP
Fix corrupted or missing store paths by redownloading or rebuilding them.
Note that this is slow because it requires computing a cryptographic hash of the contents of every path in the closure of the build.
Also note the warning under \fCnix-store --repair-path\fR.
.RS
.LP
\fBNote\fR
.PP
See \fB\fCman nix.conf\fR\fR for overriding configuration settings with command line flags.
.RE
.SH
Environment variables
.IP "\(bu" 3
\fCNIX_PROFILE\fR
.br
Location of the Nix profile. Defaults to the target of the symlink
\fC\(ti/.nix-profile\fR, if it exists, or \fC/nix/var/nix/profiles/default\fR
otherwise.
.SH
Common Environment Variables
.LP
Most Nix commands interpret the following environment variables:
.IP "\(bu" 3
\fB\fCIN_NIX_SHELL\fR\fR
.IP
Indicator that tells if the current environment was set up by
\fCnix-shell\fR. It can have the values \fCpure\fR or \fCimpure\fR.
.IP "\(bu" 3
\fB\fCNIX_PATH\fR\fR
.IP
A colon-separated list of directories used to look up the location of Nix
expressions using \fBpaths\fR
enclosed in angle brackets (i.e., \fC<path>\fR),
e.g. \fC/home/eelco/Dev:/etc/nixos\fR. It can be extended using the
\fB\fC-I\fR option\fR.
.IP
If \fCNIX_PATH\fR is not set at all, Nix will fall back to the following list in \fBimpure\fR and \fBunrestricted\fR evaluation mode:
.RS
.IP "1." 3
\fC$HOME/.nix-defexpr/channels\fR
.if n \
.sp -1
.if t \
.sp -0.25v
.IP "2." 3
\fCnixpkgs=/nix/var/nix/profiles/per-user/root/channels/nixpkgs\fR
.if n \
.sp -1
.if t \
.sp -0.25v
.IP "3." 3
\fC/nix/var/nix/profiles/per-user/root/channels\fR
.RE
.IP
If \fCNIX_PATH\fR is set to an empty string, resolving search paths will always fail.
For example, attempting to use \fC<nixpkgs>\fR will produce:
.IP
error: file \(oqnixpkgs\(cq was not found in the Nix search path
.IP "\(bu" 3
\fB\fCNIX_IGNORE_SYMLINK_STORE\fR\fR
.IP
Normally, the Nix store directory (typically \fC/nix/store\fR) is not
allowed to contain any symlink components. This is to prevent
“impure” builds. Builders sometimes “canonicalise” paths by
resolving all symlink components. Thus, builds on different machines
(with \fC/nix/store\fR resolving to different locations) could yield
different results. This is generally not a problem, except when
builds are deployed to machines where \fC/nix/store\fR resolves
differently. If you are sure that you’re not going to do that, you
can set \fCNIX_IGNORE_SYMLINK_STORE\fR to \fC1\fR.
.IP
Note that if you’re symlinking the Nix store so that you can put it
on another file system than the root file system, on Linux you’re
better off using \fCbind\fR mount points, e.g.,
.LP
.EX
$ mkdir /nix
$ mount -o bind /mnt/otherdisk/nix /nix
.EE
.IP
Consult the mount 8 manual page for details.
.IP "\(bu" 3
\fB\fCNIX_STORE_DIR\fR\fR
.IP
Overrides the location of the Nix store (default \fCprefix/store\fR).
.IP "\(bu" 3
\fB\fCNIX_DATA_DIR\fR\fR
.IP
Overrides the location of the Nix static data directory (default
\fCprefix/share\fR).
.IP "\(bu" 3
\fB\fCNIX_LOG_DIR\fR\fR
.IP
Overrides the location of the Nix log directory (default
\fCprefix/var/log/nix\fR).
.IP "\(bu" 3
\fB\fCNIX_STATE_DIR\fR\fR
.IP
Overrides the location of the Nix state directory (default
\fCprefix/var/nix\fR).
.IP "\(bu" 3
\fB\fCNIX_CONF_DIR\fR\fR
.IP
Overrides the location of the system Nix configuration directory
(default \fCprefix/etc/nix\fR).
.IP "\(bu" 3
\fB\fCNIX_CONFIG\fR\fR
.IP
Applies settings from Nix configuration from the environment.
The content is treated as if it was read from a Nix configuration file.
Settings are separated by the newline character.
.IP "\(bu" 3
\fB\fCNIX_USER_CONF_FILES\fR\fR
.IP
Overrides the location of the Nix user configuration files to load from.
.IP
The default are the locations according to the \fBXDG Base Directory Specification\fR.
See the \fBXDG Base Directories\fR sub-section for details.
.IP
The variable is treated as a list separated by the \fC:\fR token.
.IP "\(bu" 3
\fB\fCTMPDIR\fR\fR
.IP
Use the specified directory to store temporary files. In particular,
this includes temporary build directories; these can take up
substantial amounts of disk space. The default is \fC/tmp\fR.
.IP "\(bu" 3
\fB\fCNIX_REMOTE\fR\fR
.IP
This variable should be set to \fCdaemon\fR if you want to use the Nix
daemon to execute Nix operations. This is necessary in \fBmulti-user
Nix installations\fR. If the Nix
daemon\(cqs Unix socket is at some non-standard path, this variable
should be set to \fCunix://path/to/socket\fR. Otherwise, it should be
left unset.
.IP "\(bu" 3
\fB\fCNIX_SHOW_STATS\fR\fR
.IP
If set to \fC1\fR, Nix will print some evaluation statistics, such as
the number of values allocated.
.IP "\(bu" 3
\fB\fCNIX_COUNT_CALLS\fR\fR
.IP
If set to \fC1\fR, Nix will print how often functions were called during
Nix expression evaluation. This is useful for profiling your Nix
expressions.
.IP "\(bu" 3
\fB\fCGC_INITIAL_HEAP_SIZE\fR\fR
.IP
If Nix has been configured to use the Boehm garbage collector, this
variable sets the initial size of the heap in bytes. It defaults to
384 MiB. Setting it to a low value reduces memory consumption, but
will increase runtime due to the overhead of garbage collection.
.SS
XDG Base Directories
.LP
Nix follows the \fBXDG Base Directory Specification\fR.
.PP
For backwards compatibility, Nix commands will follow the standard only when \fB\fCuse-xdg-base-directories\fR\fR is enabled.
\fBNew Nix commands\fR (experimental) conform to the standard by default.
.PP
The following environment variables are used to determine locations of various state and configuration files:
.IP "\(bu" 3
[\fCXDG_CONFIG_HOME\fR]{#env-XDG\fICONFIG\fRHOME} (default \fC\(ti/.config\fR)
.if n \
.sp -1
.if t \
.sp -0.25v
.IP "\(bu" 3
[\fCXDG_STATE_HOME\fR]{#env-XDG\fISTATE\fRHOME} (default \fC\(ti/.local/state\fR)
.if n \
.sp -1
.if t \
.sp -0.25v
.IP "\(bu" 3
[\fCXDG_CACHE_HOME\fR]{#env-XDG\fICACHE\fRHOME} (default \fC\(ti/.cache\fR)
.SH
Examples
.LP
To install a package using a specific attribute path from the active Nix expression:
.LP
.EX
$ nix-env --install --attr gcc40mips
installing \(gagcc-4.0.2'
$ nix-env --install --attr xorg.xorgserver
installing \(gaxorg-server-1.2.0'
.EE
.PP
To install a specific version of \fCgcc\fR using the derivation name:
.LP
.EX
$ nix-env --install gcc-3.3.2
installing \(gagcc-3.3.2'
uninstalling \(gagcc-3.1'
.EE
.PP
Using attribute path for selecting a package is preferred,
as it is much faster and there will not be multiple matches.
.PP
Note the previously installed version is removed, since
\fC--preserve-installed\fR was not specified.
.PP
To install an arbitrary version:
.LP
.EX
$ nix-env --install gcc
installing \(gagcc-3.3.2'
.EE
.PP
To install all derivations in the Nix expression \fCfoo.nix\fR:
.LP
.EX
$ nix-env --file \(ti/foo.nix --install '.*'
.EE
.PP
To copy the store path with symbolic name \fCgcc\fR from another profile:
.LP
.EX
$ nix-env --install --from-profile /nix/var/nix/profiles/foo gcc
.EE
.PP
To install a specific \fBstore derivation\fR:
.LP
.EX
$ nix-env --install /nix/store/fibjb1bfbpm5mrsxc4mh2d8n37sxh91i-gcc-3.4.3.drv
.EE
.PP
To install a specific output path:
.LP
.EX
$ nix-env --install /nix/store/y3cgx0xj1p4iv9x0pnnmdhr8iyg741vk-gcc-3.4.3
.EE
.PP
To install from a Nix expression specified on the command-line:
.LP
.EX
$ nix-env --file ./foo.nix --install --expr \e
    'f: (f {system = \(dqi686-linux\(dq;}).subversionWithJava'
.EE
.PP
I.e., this evaluates to \fC(f: (f {system =
\(dqi686-linux\(dq;}).subversionWithJava) (import ./foo.nix)\fR, thus selecting
the \fCsubversionWithJava\fR attribute from the set returned by calling the
function defined in \fC./foo.nix\fR.
.PP
A dry-run tells you which paths will be downloaded or built from source:
.LP
.EX
$ nix-env --file '<nixpkgs>' --install --attr hello --dry-run
(dry run; not doing anything)
installing ‘hello-2.10’
this path will be fetched (0.04 MiB download, 0.19 MiB unpacked):
  /nix/store/wkhdf9jinag5750mqlax6z2zbwhqb76n-hello-2.10
  ...
.EE
.PP
To install Firefox from the latest revision in the Nixpkgs/NixOS 14.12
channel:
.LP
.EX
$ nix-env --file https://github.com/NixOS/nixpkgs/archive/nixos-14.12.tar.gz --install --attr firefox
.EE