From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 26366@debbugs.gnu.org
Subject: bug#26366: [PATCH] doc: Specify that Guix should be built from within a container.
Date: Sat, 08 Apr 2017 14:40:13 +0200 [thread overview]
Message-ID: <87bms7qdhu.fsf@gnu.org> (raw)
In-Reply-To: <20170405074943.27404-1-clement@lassieur.org> ("Clément Lassieur"'s message of "Wed, 5 Apr 2017 09:49:43 +0200")
Clément Lassieur <clement@lassieur.org> skribis:
> * doc/contributing.texi: add '--container' and '--network' options to the
> 'guix environment guix' command.
[...]
> +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
What’s the rationale? Was this to address the warnings in your first
message?
It’s possible and a good way to silence the warnings you were seeing,
but it should work fine without it too.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-04-08 12:41 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 ` bug#26366: [PATCH] doc: Specify that Guix should be built " Clément Lassieur
2017-04-08 12:40 ` Ludovic Courtès [this message]
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=87bms7qdhu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26366@debbugs.gnu.org \
--cc=clement@lassieur.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.