From: Alexander Smirnov <asmirnov@ilbers.de>
To: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/1] Add proxy support to isar-image-*.bb and buildchroot.bb
Date: Mon, 11 Dec 2017 16:15:33 +0300 [thread overview]
Message-ID: <e3df0f79-0fe5-5a96-2681-6ce5f25a5f03@ilbers.de> (raw)
In-Reply-To: <20170927120234.1541-2-andreas.reichel.ext@siemens.com>
On 09/27/2017 03:02 PM, Andreas J. Reichel wrote:
> From: Andreas Reichel <andreas.reichel.ext@siemens.com>
>
> * BB_ENV_EXTRAWHITE provides a list for variables that are kept in the
> environment by bitbake. However, isar init script clears any additional
> settings. Thus, add proxy variables to BB_ENV_EXTRAWHITE in
> isar-buildenv-internal.
>
> * Bitbake clears environment variables for each task within a recipe.
> However, bb.utils.export_proxies function can be used with an
> inline-python call to reexport the proxy settings.
>
> * Sudo loses environment variables again, thus call multistrap with sudo
> with the -E option to preserve (the already cleaned) environment for the
> task's multistrap command.
>
> Note:
> Downloads are normally done by the fetcher task, which calls a python
> function that in turn uses bb.util.export_proxies. However we have a
> non-fetcher task, which needs download capabilities as well.
>
Applied to next, thanks!
Alex
next prev parent reply other threads:[~2017-12-11 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170927120234.1541-1-andreas.reichel.ext@siemens.com>
2017-09-27 12:02 ` Andreas J. Reichel
2017-09-27 12:29 ` Andreas Reichel
2017-09-28 8:16 ` Henning Schild
2017-09-27 12:29 ` Henning Schild
2017-12-08 18:10 ` Henning Schild
2017-12-11 13:15 ` Alexander Smirnov [this message]
2017-09-11 10:55 [PATCH v2 0/1] Make do_rootfs work with proxy settings Andreas J. Reichel
2017-09-11 10:55 ` [PATCH v2 1/1] Add proxy support to isar-image-*.bb and buildchroot.bb Andreas J. Reichel
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=e3df0f79-0fe5-5a96-2681-6ce5f25a5f03@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=andreas.reichel.ext@siemens.com \
--cc=isar-users@googlegroups.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