From: Matthew McClintock <msm@freescale.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 4/6] scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITE
Date: Tue, 4 Oct 2011 17:03:05 -0500 [thread overview]
Message-ID: <1317765787-19127-4-git-send-email-msm@freescale.com> (raw)
In-Reply-To: <1317765787-19127-1-git-send-email-msm@freescale.com>
From: Kumar Gala <galak@kernel.crashing.org>
If a SOCKS5 gateway is needed for a proxy access like git it might also
require authentication to the proxy via a password and username. Adding
SOCKS5_USER & SOCKS5_PASSWD to BB_ENV_EXTRAWHITE allow for automation
of the authentication request to occur when something like a git fetch
is going through the proxy.
This patch requires the bitbake patch to add extra exportvars so
these variables get passed from Env -> bitbake -> fetcher
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Matthew McClintock <msm@freescale.com>
---
This requires a bitbake patch that was just sent:
http://lists.linuxtogo.org/pipermail/bitbake-devel/2011-October/001453.html
scripts/oe-buildenv-internal | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/scripts/oe-buildenv-internal b/scripts/oe-buildenv-internal
index 61ac18c..21b92b0 100755
--- a/scripts/oe-buildenv-internal
+++ b/scripts/oe-buildenv-internal
@@ -70,5 +70,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 SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND"
+export BB_ENV_EXTRAWHITE="MACHINE DISTRO TCMODE TCLIBC http_proxy ftp_proxy https_proxy all_proxy ALL_PROXY no_proxy SSH_AGENT_PID SSH_AUTH_SOCK BB_SRCREV_POLICY SDKMACHINE BB_NUMBER_THREADS PARALLEL_MAKE GIT_PROXY_COMMAND GIT_PROXY_IGNORE SOCKS5_PASSWD SOCKS5_USER"
--
1.7.6.1
next prev parent reply other threads:[~2011-10-04 22:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 22:03 [PATCH 1/6] Fix mdadm for powerpc64 Matthew McClintock
2011-10-04 22:03 ` [PATCH 2/6] Fix perl for powerpc64 build Matthew McClintock
2011-10-05 11:46 ` Richard Purdie
2011-10-05 19:04 ` McClintock Matthew-B29882
2011-10-07 15:52 ` Richard Purdie
2011-10-07 16:07 ` McClintock Matthew-B29882
2011-10-04 22:03 ` [PATCH 3/6] Add new IMAGE_CLASSES variable for classes for image generation Matthew McClintock
2011-10-05 22:52 ` McClintock Matthew-B29882
2011-10-05 23:53 ` Richard Purdie
2011-10-06 0:25 ` McClintock Matthew-B29882
2011-10-11 16:44 ` McClintock Matthew-B29882
2011-10-04 22:03 ` Matthew McClintock [this message]
2011-10-05 13:25 ` [PATCH 4/6] scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITE Richard Purdie
2011-10-04 22:03 ` [PATCH 5/6] Fix sysprof for powerpc64 Matthew McClintock
2011-10-05 0:05 ` Khem Raj
2011-10-05 6:44 ` McClintock Matthew-B29882
2011-10-05 11:35 ` Richard Purdie
2011-10-05 16:46 ` Khem Raj
2011-10-05 16:48 ` McClintock Matthew-B29882
2011-10-05 17:06 ` Khem Raj
2011-10-05 17:10 ` Saul Wold
2011-10-05 18:30 ` Phil Blundell
2011-10-05 18:41 ` McClintock Matthew-B29882
2011-10-05 19:13 ` Khem Raj
2011-10-04 22:03 ` [PATCH 6/6] Bring libnl up to date with meta-openebedded Matthew McClintock
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=1317765787-19127-4-git-send-email-msm@freescale.com \
--to=msm@freescale.com \
--cc=openembedded-core@lists.openembedded.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