From: ludo@gnu.org (Ludovic Courtès)
To: Jookia <166291@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] svn-download: Respect current-http-proxy when downloading.
Date: Thu, 03 Mar 2016 17:39:21 +0100 [thread overview]
Message-ID: <87povbcy86.fsf@gnu.org> (raw)
In-Reply-To: <20160303043205.GA28472@novena-choice-citizen.lan> (Jookia's message of "Thu, 3 Mar 2016 15:32:05 +1100")
Jookia <166291@gmail.com> skribis:
> On Sun, Feb 28, 2016 at 05:44:18PM +0100, Ludovic Courtès wrote:
>> > + (define proxy-config
>> > + (if (current-http-proxy)
>> > + (and-let* ((proxy-uri (string->uri (current-http-proxy)))
>> > + (proxy-host (uri-host proxy-uri))
>> > + (proxy-port (number->string (uri-port proxy-uri)))
>> > + (config-host "servers:global:http-proxy-host=")
>> > + (config-port "servers:global:http-proxy-port="))
>> > + `("--config-option" ,(string-append config-host proxy-host)
>> > + "--config-option" ,(string-append config-port proxy-port)))
>> > + '()))
>>
>> I would suggest using an explicit (getenv "http_proxy") instead of
>> (current-http-proxy) since the latter is specific to the (web …)
>> modules, which are not involved here.
>
> Sorry for the reply, now that I have an RFC for the coreboot patches I've looked
> back at this. The URI module is also in the web module, and I'm not sure how I
> feel about rewriting a URI parser to get the host and port out of http_proxy.
Of course you should keep using ‘string->uri’, no problem with that.
I’m just saying that the code should explicitly check for the
‘http_proxy’ environment variable instead of using the
‘current-http-proxy’ SRFI-9 parameter.
WDYT?
Ludo’.
next prev parent reply other threads:[~2016-03-03 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 12:37 [PATCH 1/2] svn-download: Respect current-http-proxy when downloading Jookia
2016-02-28 16:44 ` Ludovic Courtès
2016-02-28 21:45 ` Jookia
2020-03-15 11:22 ` levenson
2020-03-15 12:45 ` Jookia
2020-03-15 18:04 ` Leo Famulari
2016-03-03 4:32 ` Jookia
2016-03-03 16:39 ` Ludovic Courtès [this message]
2016-03-03 16:44 ` Jookia
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=87povbcy86.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=166291@gmail.com \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).