all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: 26366@debbugs.gnu.org
Subject: bug#26366: [PATCH] doc: Specify that Guix should be built from within a container.
Date: Wed,  5 Apr 2017 09:49:43 +0200	[thread overview]
Message-ID: <20170405074943.27404-1-clement@lassieur.org> (raw)
In-Reply-To: <87inmjcn1o.fsf@lassieur.org>

* doc/contributing.texi: add '--container' and '--network' options to the
'guix environment guix' command.
---
 doc/contributing.texi | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index bbc93424b..dbafa4139 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -45,19 +45,19 @@ the installation instructions (@pxref{Requirements}).
 @end itemize
 
 The easiest way to set up a development environment for Guix is, of
-course, by using Guix!  The following command starts a new shell where
-all the dependencies and appropriate environment variables are set up to
-hack on Guix:
+course, by using Guix!  The following command starts a new shell within
+an isolated container where all the dependencies and appropriate
+environment variables are set up to hack on Guix:
 
 @example
-guix environment guix
+guix environment --container --network guix
 @end example
 
 @xref{Invoking guix environment}, for more information on that command.
 Extra dependencies can be added with @option{--ad-hoc}:
 
 @example
-guix environment guix --ad-hoc help2man git strace
+guix environment --container --network guix --ad-hoc help2man git strace
 @end example
 
 Run @command{./bootstrap} to generate the build system infrastructure
-- 
2.12.2

  reply	other threads:[~2017-04-05  7:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  7:48 bug#26366: Building Guix from within a container Clément Lassieur
2017-04-05  7:49 ` Clément Lassieur [this message]
2017-04-08 12:40   ` bug#26366: [PATCH] doc: Specify that Guix should be built " Ludovic Courtès
2017-04-13 16:29     ` Clément Lassieur
2017-04-13 21:23       ` Ludovic Courtès
2017-04-13 21:32         ` Clément Lassieur
2017-04-14  7:54           ` Ludovic Courtès
2017-04-05 12:26 ` bug#26366: Building Guix " Clément Lassieur
2017-04-06 15:10   ` Clément Lassieur
2017-04-13 16:45     ` Clément Lassieur
2017-04-13 21:24       ` Ludovic Courtès
2017-04-13 21:27         ` Clément Lassieur
2017-04-08 12:38 ` Ludovic Courtès
2017-04-08 12:57   ` Pjotr Prins
2017-04-08 13:54     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170405074943.27404-1-clement@lassieur.org \
    --to=clement@lassieur.org \
    --cc=26366@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.