summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAndreas Enge <andreas@enge.fr>2016-02-13 20:04:10 +0100
committerAndreas Enge <andreas@enge.fr>2016-02-16 16:37:37 +0100
commit4d4c481601db228a80344a77223b063635ffe533 (patch)
tree1b9aae7e1b1050721487cc4d92b9e1bd5acaf1a8 /doc
parentb736776255f7232003af2e2c1e6ecf203dfa47f7 (diff)
downloadguix-patches-4d4c481601db228a80344a77223b063635ffe533.tar
guix-patches-4d4c481601db228a80344a77223b063635ffe533.tar.gz
doc: Move paragraphs in description of guix archive.
* doc/guix.texi ("invoking guix archive"): Move paragraph describing basic invocation from the end to the beginning of the section.
Diffstat (limited to 'doc')
-rw-r--r--doc/guix.texi46
1 files changed, 24 insertions, 22 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index bac73890e1..0ff5cfc523 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -2004,8 +2004,30 @@ useful to Guix developers.
The @command{guix archive} command allows users to @dfn{export} files
from the store into a single archive, and to later @dfn{import} them.
In particular, it allows store files to be transferred from one machine
-to the store on another machine. For example, to transfer the @code{emacs}
-package to a machine connected over SSH, one would run:
+to the store on another machine.
+
+To export store files as an archive to standard output, run:
+
+@example
+guix archive --export @var{options} @var{specifications}...
+@end example
+
+@var{specifications} may be either store file names or package
+specifications, as for @command{guix package} (@pxref{Invoking guix
+package}). For instance, the following command creates an archive
+containing the @code{gui} output of the @code{git} package and the main
+output of @code{emacs}:
+
+@example
+guix archive --export git:gui /gnu/store/...-emacs-24.3 > great.nar
+@end example
+
+If the specified packages are not built yet, @command{guix archive}
+automatically builds them. The build process may be controlled with the
+common build options (@pxref{Common Build Options}).
+
+To transfer the @code{emacs} package to a machine connected over SSH,
+one would run:
@example
guix archive --export -r emacs | ssh the-machine guix archive --import
@@ -2127,26 +2149,6 @@ archive contents coming from possibly untrusted substitute servers.
@end table
-To export store files as an archive to standard output, run:
-
-@example
-guix archive --export @var{options} @var{specifications}...
-@end example
-
-@var{specifications} may be either store file names or package
-specifications, as for @command{guix package} (@pxref{Invoking guix
-package}). For instance, the following command creates an archive
-containing the @code{gui} output of the @code{git} package and the main
-output of @code{emacs}:
-
-@example
-guix archive --export git:gui /gnu/store/...-emacs-24.3 > great.nar
-@end example
-
-If the specified packages are not built yet, @command{guix archive}
-automatically builds them. The build process may be controlled with the
-common build options (@pxref{Common Build Options}).
-
@c *********************************************************************
@include emacs.texi