Document $NIX_PATH / -I

This commit is contained in:
Eelco Dolstra 2012-05-09 19:06:13 -04:00
parent a58efdb69b
commit 7a213ffc69
3 changed files with 66 additions and 13 deletions

View file

@ -10,6 +10,40 @@
<variablelist xml:id="env-common"> <variablelist xml:id="env-common">
<varlistentry><term><envar>NIX_PATH</envar></term>
<listitem>
<para>A colon-separated list of directories used to look up Nix
expressions enclosed in angle brackets (i.e.,
<literal>&lt;<replaceable>path</replaceable>></literal>). For
instance, the value
<screen>
/home/eelco/Dev:/etc/nixos</screen>
will cause Nix to look for paths relative to
<filename>/home/eelco/Dev</filename> and
<filename>/etc/nixos</filename>, in that order. It is also
possible to match paths against a prefix. For example, the value
<screen>
nixpkgs=/home/eelco/Dev/nixpkgs-branch:/etc/nixos</screen>
will cause Nix to search for
<literal>&lt;nixpkgs/<replaceable>path</replaceable>></literal> in
<filename>/home/eelco/Dev/nixpkgs-branch/<replaceable>path</replaceable></filename>
and
<filename>/etc/nixos/nixpkgs/<replaceable>path</replaceable></filename>.
</para>
<para>The search path can be extended using the
<option>-I</option> option, which takes precedence over
<envar>NIX_PATH</envar>.</para></listitem>
</varlistentry>
<varlistentry><term><envar>NIX_IGNORE_SYMLINK_STORE</envar></term> <varlistentry><term><envar>NIX_IGNORE_SYMLINK_STORE</envar></term>
<listitem> <listitem>
@ -120,9 +154,12 @@ $ mount -o bind /mnt/otherdisk/nix /nix</screen>
which is a program (typically some script) that Nix will call which is a program (typically some script) that Nix will call
whenever it wants to build a derivation. This is used to implement whenever it wants to build a derivation. This is used to implement
distributed builds<phrase condition="manual"> (see <xref distributed builds<phrase condition="manual"> (see <xref
linkend="chap-distributed-builds" />)</phrase>. The protocol by linkend="chap-distributed-builds" />)</phrase>.</para>
<!--
The protocol by
which the calling Nix process and the build hook communicate is as which the calling Nix process and the build hook communicate is as
follows.</para> follows.
<para>The build hook is called with the following command-line <para>The build hook is called with the following command-line
arguments: arguments:
@ -234,6 +271,7 @@ $ mount -o bind /mnt/otherdisk/nix /nix</screen>
<literal>0</literal> indicates that the hook has failed. An exit <literal>0</literal> indicates that the hook has failed. An exit
code equal to 100 means that the remote build failed (as opposed to, code equal to 100 means that the remote build failed (as opposed to,
e.g., a network error).</para> e.g., a network error).</para>
-->
</listitem> </listitem>
@ -256,12 +294,13 @@ $ mount -o bind /mnt/otherdisk/nix /nix</screen>
<listitem><para>This variable contains the paths of remote Nix <listitem><para>This variable contains the paths of remote Nix
installations from whichs paths can be copied, separated by colons. installations from whichs paths can be copied, separated by colons.
See <xref linkend="sec-sharing-packages" /> for details. Each path <phrase condition="manual">See <xref linkend="sec-sharing-packages"
should be the <filename>/nix</filename> directory of a remote Nix /> for details.</phrase> Each path should be the
installation (i.e., not the <filename>/nix/store</filename> <filename>/nix</filename> directory of a remote Nix installation
directory). The paths are subject to globbing, so you can set it so (i.e., not the <filename>/nix/store</filename> directory). The
something like <literal>/var/run/nix/remote-stores/*/nix</literal> paths are subject to globbing, so you can set it so something like
and mount multiple remote filesystems in <literal>/var/run/nix/remote-stores/*/nix</literal> and mount
multiple remote filesystems in
<literal>/var/run/nix/remote-stores</literal>.</para> <literal>/var/run/nix/remote-stores</literal>.</para>
<para>Note that if youre building through the <link <para>Note that if youre building through the <link

View file

@ -14,15 +14,15 @@
<replaceable>number</replaceable> <replaceable>number</replaceable>
</arg> </arg>
<arg> <arg>
<arg><option>--cores</option></arg> <option>--cores</option>
<replaceable>number</replaceable> <replaceable>number</replaceable>
</arg> </arg>
<arg> <arg>
<arg><option>--max-silent-time</option></arg> <option>--max-silent-time</option>
<replaceable>number</replaceable> <replaceable>number</replaceable>
</arg> </arg>
<arg> <arg>
<arg><option>--timeout</option></arg> <option>--timeout</option>
<replaceable>number</replaceable> <replaceable>number</replaceable>
</arg> </arg>
<arg><option>--keep-going</option></arg> <arg><option>--keep-going</option></arg>
@ -33,6 +33,10 @@
<arg><option>--readonly-mode</option></arg> <arg><option>--readonly-mode</option></arg>
<arg><option>--log-type</option> <replaceable>type</replaceable></arg> <arg><option>--log-type</option> <replaceable>type</replaceable></arg>
<arg><option>--show-trace</option></arg> <arg><option>--show-trace</option></arg>
<arg>
<option>-I</option>
<replaceable>path</replaceable>
</arg>
<sbr /> <sbr />
</nop> </nop>

View file

@ -341,6 +341,16 @@
</varlistentry> </varlistentry>
<varlistentry><term><option>-I</option> <replaceable>path</replaceable></term>
<listitem><para>Add a path to the Nix expression search path. See
the <envar>NIX_PATH</envar> environment variable for details. Paths
added through <option>-I</option> take precedence over
<envar>NIX_PATH</envar>.</para></listitem>
</varlistentry>
</variablelist> </variablelist>