From: Petter <petter@mykolab.ch>
To: guix-devel@gnu.org
Subject: [PATCH] doc: Mention "guix pull" during installation.
Date: Fri, 16 Dec 2016 09:38:02 +0100 [thread overview]
Message-ID: <82b3233597949c866c26628054117ee3@mykolab.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 176 bytes --]
Hi,
Some new users don't run `guix pull` before installing, and can have a
less good experience because of this. Proposing a patch to add this to
the manual.
Thanks,
Petter
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-Mention-guix-pull-during-installation.patch --]
[-- Type: text/x-diff; name=0001-doc-Mention-guix-pull-during-installation.patch, Size: 1112 bytes --]
From 2340158e5454cbb3050840821bf0fd1965d2fe79 Mon Sep 17 00:00:00 2001
From: Petter <petter@mykolab.ch>
Date: Fri, 16 Dec 2016 09:28:32 +0100
Subject: [PATCH] doc: Mention "guix pull" during installation.
* doc/guix.texi (Proceeding with the Installation): Add "guix pull".
---
doc/guix.texi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index 46ed451..cda90ed 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -6863,6 +6863,14 @@ rather than kept in memory. This is necessary because the first phase of
the @command{guix system init} command (see below) entails downloads or
builds to @file{/gnu/store} which, initially, is an in-memory file system.
+At this point it is advisable to update the system, especially if the
+installer is more than a few weeks old. Then most, if not all, packages
+will be available as substitutes.
+
+@example
+guix pull
+@end example
+
Next, you have to edit a file and
provide the declaration of the operating system to be installed. To
that end, the installation system comes with three text editors: GNU nano
--
2.10.1
next reply other threads:[~2016-12-16 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 8:38 Petter [this message]
2016-12-17 17:38 ` [PATCH] doc: Mention "guix pull" during installation Leo Famulari
2016-12-18 11:00 ` Ludovic Courtès
2016-12-19 7:41 ` Alex Sassmannshausen
2016-12-18 12:05 ` Theodoros Foradis
2016-12-19 8:09 ` Ra
2016-12-19 10:52 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82b3233597949c866c26628054117ee3@mykolab.ch \
--to=petter@mykolab.ch \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).