From: Darren Hart <dvhart@linux.intel.com>
To: Poky <poky@yoctoproject.org>,
openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 5/9] oe-buildenv-internal: Add upper and lower case proxy vars to BB_ENV_EXTRAWHITE
Date: Tue, 5 Feb 2013 14:52:47 -0800 [thread overview]
Message-ID: <8026dc1cceecd878a7428cc20e78454b00718dcd.1360104547.git.dvhart@linux.intel.com> (raw)
In-Reply-To: <cover.1360104547.git.dvhart@linux.intel.com>
In-Reply-To: <cover.1360104547.git.dvhart@linux.intel.com>
Applications are inconsistent in their use of upper and lower case proxy
variables. Curl, for example, specifies NO_PROXY (not no_proxy) in the
man page (changed in 2009 [1]). Avoid proxy issues by ensuring both the
upper and lower case versions of each proxy variable are available in
the environment for the fetcher commands.
Add FTPS_PROXY and ftps_proxy to the list as well.
1. http://curl.haxx.se/mail/tracker-2009-04/0012.html
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
---
scripts/oe-buildenv-internal | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/scripts/oe-buildenv-internal b/scripts/oe-buildenv-internal
index 044b6f9..7783574 100755
--- a/scripts/oe-buildenv-internal
+++ b/scripts/oe-buildenv-internal
@@ -80,4 +80,4 @@ unset BITBAKEDIR
# Used by the runqemu script
export BUILDDIR
export PATH
-export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy NO_PROXY SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS BB_NO_NETWORK PARALLEL_MAKE GIT_PROXY_COMMAND SOCKS5_PASSWD SOCKS5_USER SCREENDIR"
+export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC HTTP_PROXY http_proxy HTTPS_PROXY https_proxy FTP_PROXY ftp_proxy FTPS_PROXY ftps_proxy ALL_PROXY all_proxy NO_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS BB_NO_NETWORK PARALLEL_MAKE GIT_PROXY_COMMAND SOCKS5_PASSWD SOCKS5_USER SCREENDIR"
--
1.7.5.4
next prev parent reply other threads:[~2013-02-05 23:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 22:52 [PATCH V2 0/9] Git fetcher and proxy handling updates Darren Hart
2013-02-05 22:52 ` [PATCH 1/9] bitbake: fetch2: Print the complete SRCREV variable name when INVALID Darren Hart
2013-02-05 22:52 ` [PATCH 2/9] bitbake: fetch2: Export upper and lower case environment variables Darren Hart
2013-02-05 22:52 ` [PATCH 3/9] bitbake: fetch2: Remove broken git variables from the environment Darren Hart
2013-02-05 22:52 ` [PATCH 4/9] oe-buildenv-internal: Remove GIT variables from BB_ENV_EXTRAWHITE Darren Hart
2013-02-05 22:52 ` Darren Hart [this message]
2013-02-05 22:52 ` [PATCH 6/9] base.bbclass: Remove generate_git_config() Darren Hart
2013-02-05 22:52 ` [PATCH 7/9] oe-git-proxy: Add a new comprehensive git proxy script Darren Hart
2013-02-05 23:51 ` Otavio Salvador
2013-02-06 0:04 ` Darren Hart
2013-02-06 0:09 ` Otavio Salvador
2013-02-06 0:16 ` Darren Hart
2013-02-05 22:52 ` [PATCH 8/9] meta-yocto: Document new oe-git-proxy in site.conf.sample Darren Hart
2013-02-06 0:24 ` Otavio Salvador
2013-02-06 0:29 ` Darren Hart
2013-02-05 22:52 ` [PATCH 9/9] oe-git-proxy*: Remove previous git proxy solutions Darren Hart
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=8026dc1cceecd878a7428cc20e78454b00718dcd.1360104547.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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