diff options
| author | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2013-01-02 22:36:08 +0100 |
|---|---|---|
| committer | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2013-01-02 22:36:08 +0100 |
| commit | f12492c66dc5c71c22ce2eb1788dacd86b1dfb1f (patch) | |
| tree | a6abd9c9ab31c86fe6090599fe75193b37d9a062 | |
| parent | aebea2e489a21af260e7a654b0313efe042fbf9d (diff) | |
| download | guix-f12492c66dc5c71c22ce2eb1788dacd86b1dfb1f.tar.gz | |
Manual: Fix "nix-store --export" example
| -rw-r--r-- | doc/manual/package-management.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/manual/package-management.xml b/doc/manual/package-management.xml index ca19b13258..a0ada63e55 100644 --- a/doc/manual/package-management.xml +++ b/doc/manual/package-management.xml @@ -538,7 +538,7 @@ dependencies) to a file, and then unpack that file into another Nix store. For example, <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 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: <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> 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 <filename>/mnt/nix</filename>, then it will just copy from there instead of building it from source.</para> - + </section> |