From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] oe-init-build-env: allow GIT_SSL_CAINFO from external environment
Date: Tue, 24 May 2016 08:25:58 +0100 [thread overview]
Message-ID: <1464074758.9570.34.camel@linuxfoundation.org> (raw)
In-Reply-To: <8f3a29655613c98c31c41ade3134540a96f074a7.1464057554.git.paul.eggleton@linux.intel.com>
On Tue, 2016-05-24 at 14:40 +1200, Paul Eggleton wrote:
> buildtools-tarball sets GIT_SSL_CAINFO so that the included
> ca-certificates can be used by git; that can't work however unless
> the GIT_SSL_CAINFO is still set in the environment in which git gets
> run by the fetcher, so allow it through from the external
> environment.
>
> Fixes [YOCTO #9666].
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> scripts/oe-buildenv-internal | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Would it make more sense to just list this in
lib/bb/fetch2/__init__.py:runfetchcmd() instead?
In some ways I'd be in favour of pruning the main bitbake.conf list in
favour of just listing things like proxy variables there specifically
in the fetcher.
If users want to be able to configure that list, we could expose that
list from bitbake too...
Cheers,
Richard
next prev parent reply other threads:[~2016-05-24 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 2:40 [PATCH 0/2] Allow GIT_SSL_CAINFO set by buildtools-tarball to work Paul Eggleton
2016-05-24 2:40 ` [PATCH 1/2] oe-init-build-env: allow GIT_SSL_CAINFO from external environment Paul Eggleton
2016-05-24 7:25 ` Richard Purdie [this message]
2016-05-24 10:23 ` Paul Eggleton
2016-05-24 2:40 ` [PATCH 2/2] conf/bitbake.conf: whitelist GIT_SSL_CAINFO Paul Eggleton
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=1464074758.9570.34.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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