alois31/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity

Manual: Fix "nix-store --export" example

Browse source
This commit is contained in:
Eelco Dolstra 2013-01-02 22:36:08 +01:00
parent aebea2e489
commit f12492c66d
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/manual/package-management.xml
View file

@ -538,7 +538,7 @@ dependencies) to a file, and then unpack that file into another Nix
store. For example, store. For example,
<screen> <screen>
$ nix-store --export $(type -p firefox) > firefox.closure</screen> $ nix-store --export $(nix-store -qR $(type -p firefox)) > firefox.closure</screen>
writes the closure of Firefox to a file. You can then copy this file writes the closure of Firefox to a file. You can then copy this file
to another machine and install the closure: to another machine and install the closure:
@ -552,7 +552,7 @@ another command, e.g. to copy and install a closure directly to/on
another machine: another machine:
<screen> <screen>
$ nix-store --export $(type -p firefox) | bzip2 | \ $ nix-store --export $(nix-store -qR $(type -p firefox)) | bzip2 | \
ssh alice@itchy.example.org "bunzip2 | nix-store --import"</screen> ssh alice@itchy.example.org "bunzip2 | nix-store --import"</screen>
But note that <command>nix-copy-closure</command> is generally more But note that <command>nix-copy-closure</command> is generally more
@ -583,7 +583,7 @@ $ nix-env -i firefox</screen>
and Nix has to build a path that it sees is already present in 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 <filename>/mnt/nix</filename>, then it will just copy from there
instead of building it from source.</para> instead of building it from source.</para>
</section> </section>