guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

01/04: doc: Move paragraphs in description of guix archive.


From: Andreas Enge
Subject: 01/04: doc: Move paragraphs in description of guix archive.
Date: Tue, 16 Feb 2016 15:38:35 +0000

andreas pushed a commit to branch master
in repository guix.

commit 4d4c481601db228a80344a77223b063635ffe533
Author: Andreas Enge <address@hidden>
Date:   Sat Feb 13 20:04:10 2016 +0100

    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.
---
 doc/guix.texi |   46 ++++++++++++++++++++++++----------------------
 1 files changed, 24 insertions(+), 22 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index bac7389..0ff5cfc 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:
+
address@hidden
+guix archive --export @var{options} @var{specifications}...
address@hidden example
+
address@hidden 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}:
+
address@hidden
+guix archive --export git:gui /gnu/store/...-emacs-24.3 > great.nar
address@hidden 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:
-
address@hidden
-guix archive --export @var{options} @var{specifications}...
address@hidden example
-
address@hidden 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}:
-
address@hidden
-guix archive --export git:gui /gnu/store/...-emacs-24.3 > great.nar
address@hidden 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
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]