GNU bug report logs - #26366
Building Guix from within a container

Previous Next

Full log

Message #8 received at 26366 <at> debbugs.gnu.org (full text, mbox):

From: Clément Lassieur <clement <at> lassieur.org>
To: 26366 <at> debbugs.gnu.org
Subject: [PATCH] doc: Specify that Guix should be built from within a
 container.
Date: Wed,  5 Apr 2017 09:49:43 +0200

* 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.