From b1af336132cfe8a6e4c54912cc512f8c28d4ebf3 Mon Sep 17 00:00:00 2001
From: Eelco Dolstra <eelco.dolstra@logicblox.com>
Date: Tue, 16 Sep 2014 14:49:00 +0200
Subject: Undocument NIX_OTHER_STORES

---
 doc/manual/packages/sharing-packages.xml | 27 +--------------------------
 1 file changed, 1 insertion(+), 26 deletions(-)

(limited to 'doc/manual/packages')

diff --git a/doc/manual/packages/sharing-packages.xml b/doc/manual/packages/sharing-packages.xml
index 573b7c1e77a6..8fab15f7ef2d 100644
--- a/doc/manual/packages/sharing-packages.xml
+++ b/doc/manual/packages/sharing-packages.xml
@@ -53,30 +53,5 @@ But note that <command>nix-copy-closure</command> is generally more
 efficient in this example because it only copies paths that are not
 already present in the target Nix store.</para>
 
-<para>Finally, if you can mount the Nix store of a remote machine in
-your local filesystem, Nix can copy paths from the remote Nix store to
-the local Nix store <emphasis>on demand</emphasis>.  For instance,
-suppose that you mount a remote machine containing a Nix store via
-<command
-xlink:href="http://fuse.sourceforge.net/sshfs.html">sshfs</command>:
 
-<screen>
-$ sshfs alice@itchy.example.org:/ /mnt</screen>
-
-You should then set the <envar>NIX_OTHER_STORES</envar> environment
-variable to tell Nix about this remote Nix store:
-
-<screen>
-$ export NIX_OTHER_STORES=/mnt/nix</screen>
-
-Then if you do any Nix operation, e.g.
-
-<screen>
-$ nix-env -i firefox</screen>
-
-and Nix has to build a path that it sees is already present in
-<filename>/mnt/nix</filename>, then it will just copy from there
-instead of building it from source.</para>
-
-
-</chapter>
\ No newline at end of file
+</chapter>
-- 
cgit 1.4.1