From: ng0 <contact.ng0@cryptolab.net>
To: help-guix@gnu.org
Subject: Proxy documentation is not clear
Date: Sun, 19 Feb 2017 17:06:23 +0000 [thread overview]
Message-ID: <20170219170623.sdtm536s7joncoqf@wasp> (raw)
doc/guix.html/Build-Environment-Setup.html#index-http_005fproxy reads:
The daemon also honors the http_proxy environment variable for HTTP downloads it performs, be it for fixed-output derivations (see Derivations) or for substitutes (see Substitutes).
If you are installing Guix as an unprivileged user, it is still possible to run guix-daemon provided you pass --disable-chroot. However, build processes will not be isolated from one another, and not from the rest of the system. Thus, build processes may interfere with each other, and may access programs, libraries, and other files available on the system—making it much harder to view them as pure functions.
... This links to:
doc/guix.html/Derivations.html#Derivations
and
doc/guix.html/Substitutes.html#Substitutes
where the substitutes page reads:
Substitutes are downloaded over HTTP or HTTPS. The http_proxy environment variable can be set in the environment of guix-daemon and is honored for downloads of substitutes. Note that the value of http_proxy in the environment where guix build, guix package, and other client commands are run has absolutely no effect.
None of these pages provides any example or further explanation on how
this could be achieved, for example to make Guix use a socks5 proxy
systemwide. I know how this can be achieved with iptables etc, but it
would be better if the documentation is fixed. I have no idea how in
this case as the documentation is not clear.
next reply other threads:[~2017-02-19 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 17:06 ng0 [this message]
2017-02-21 3:32 ` Proxy documentation is not clear Leo Famulari
2017-02-21 9:43 ` ng0
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=20170219170623.sdtm536s7joncoqf@wasp \
--to=contact.ng0@cryptolab.net \
--cc=help-guix@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.