From: Leo Famulari <leo@famulari.name>
To: help-guix@gnu.org
Subject: Re: Proxy documentation is not clear
Date: Mon, 20 Feb 2017 22:32:40 -0500 [thread overview]
Message-ID: <20170221033240.GA19206@jasmine> (raw)
In-Reply-To: <20170219170623.sdtm536s7joncoqf@wasp>
On Sun, Feb 19, 2017 at 05:06:23PM +0000, ng0 wrote:
> 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.
It depends on how you start the daemon. For systemd, you can set the
environment variable from the service file. I'm not sure how to pass
this variable to the daemon on GuixSD.
next prev parent reply other threads:[~2017-02-21 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 17:06 Proxy documentation is not clear ng0
2017-02-21 3:32 ` Leo Famulari [this message]
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
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=20170221033240.GA19206@jasmine \
--to=leo@famulari.name \
--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.
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).