From: Ben Lutgens <lamer@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] HTTP_PROXY var in make.conf has issues
Date: Mon, 27 May 2002 14:27:17 -0500 [thread overview]
Message-ID: <20020527192717.GD24425@rtfm.sistina.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
All, the HTTP_PROXY variable we have in make.conf and friends isn't
recognized by wget. Setting as HTTP_PROXY is completely ignored by wget and
the other fetchcommands ( prozilla and lukemftp are essentially ftp
applications and they don't tend to like proxies anyway ). I see very
little reason to leave the variable as HTTP_PROXY when it should be defined
like so
http_proxy="proxy.domain.tld:3128"
A band-aid would be to set the following in either make.conf, make.globals
or the like
http_proxy="${HTTP_PROXY}" or have portage interpret HTTP_PROXY and pass it
to the environment in both ways (which seems really dumb to me)
This is probably also a good FAQ question. I'll post to the forums about it
as well.
--
Ben Lutgens | http://people.sistina.com/~blutgens/
System Administrator | http://www.sistina.com/
Sistina Software Inc. |
"I got a wife and kids too but you don't see me out here stealing Imperial
Droids now do ya?"
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2002-05-27 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020527192717.GD24425@rtfm.sistina.com \
--to=lamer@gentoo.org \
--cc=gentoo-dev@gentoo.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