Rename files

This commit is contained in:
Eelco Dolstra 2014-12-14 01:07:23 +01:00
parent 4c4e891652
commit 9c830394ec
4 changed files with 26 additions and 29 deletions

View file

@ -0,0 +1,10 @@
<part xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xi="http://www.w3.org/2001/XInclude"
version="5.0">
<title>Advanced Topics</title>
<xi:include href="distributed-builds.xml" />
</part>

View file

@ -2,9 +2,18 @@
xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xi="http://www.w3.org/2001/XInclude"
version="5.0" version="5.0"
xml:id="ch-enabling-builds"> xml:id='chap-distributed-builds'>
<title>Enabling Distributed Builds</title> <title>Distributed Builds</title>
<para>Nix supports distributed builds, where a local Nix installation can
forward Nix builds to other machines over the network. This allows
multiple builds to be performed in parallel (thus improving
performance) and allows Nix to perform multi-platform builds in a
semi-transparent way. For instance, if you perform a build for a
<literal>powerpc-darwin</literal> on an <literal>i686-linux</literal>
machine, Nix can automatically forward the build to a
<literal>powerpc-darwin</literal> machine, if available.</para>
<para>You can enable distributed builds by setting the environment <para>You can enable distributed builds by setting the environment
variable <envar>NIX_BUILD_HOOK</envar> to point to a program that Nix variable <envar>NIX_BUILD_HOOK</envar> to point to a program that Nix
@ -41,7 +50,7 @@ example configuration is shown in <xref linkend='ex-remote-systems'
bits of information: bits of information:
<orderedlist> <orderedlist>
<listitem><para>The name of the remote machine, with optionally the <listitem><para>The name of the remote machine, with optionally the
user under which the remote build should be performed. This is user under which the remote build should be performed. This is
actually passed as an argument to <command>ssh</command>, so it can actually passed as an argument to <command>ssh</command>, so it can
@ -73,9 +82,9 @@ bits of information:
<filename>build-remote.pl</filename> will only perform the <filename>build-remote.pl</filename> will only perform the
derivation on a machine that has the specified features. For derivation on a machine that has the specified features. For
instance, the attribute instance, the attribute
<programlisting> <programlisting>
requiredSystemFeatures = [ "kvm" ]; requiredSystemFeatures = [ "kvm" ];
</programlisting> </programlisting>
will cause the build to be performed on a machine that has the will cause the build to be performed on a machine that has the
@ -103,4 +112,4 @@ running, they should use the same <envar>NIX_CURRENT_LOAD</envar>
file. Maybe in the future <filename>build-remote.pl</filename> will file. Maybe in the future <filename>build-remote.pl</filename> will
look at the actual remote load.</para> look at the actual remote load.</para>
</chapter> </chapter>

View file

@ -1,22 +0,0 @@
<part xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xi="http://www.w3.org/2001/XInclude"
version="5.0"
xml:id='chap-distributed-builds'>
<title>Distributed Builds</title>
<partintro>
<para>Nix supports distributed builds, where a local Nix installation can
forward Nix builds to other machines over the network. This allows
multiple builds to be performed in parallel (thus improving
performance) and allows Nix to perform multi-platform builds in a
semi-transparent way. For instance, if you perform a build for a
<literal>powerpc-darwin</literal> on an <literal>i686-linux</literal>
machine, Nix can automatically forward the build to a
<literal>powerpc-darwin</literal> machine, if available.</para>
</partintro>
<xi:include href="enabling-builds.xml" />
</part>

View file

@ -41,7 +41,7 @@
<xi:include href="installation/installation.xml" /> <xi:include href="installation/installation.xml" />
<xi:include href="packages/package-management.xml" /> <xi:include href="packages/package-management.xml" />
<xi:include href="expressions/writing-nix-expressions.xml" /> <xi:include href="expressions/writing-nix-expressions.xml" />
<xi:include href="builds/build-farm.xml" /> <xi:include href="advanced-topics/advanced-topics.xml" />
<xi:include href="command-ref/command-ref.xml" /> <xi:include href="command-ref/command-ref.xml" />
<xi:include href="troubleshooting/troubleshooting.xml" /> <xi:include href="troubleshooting/troubleshooting.xml" />
<xi:include href="glossary/glossary.xml" /> <xi:include href="glossary/glossary.xml" />