[OE-core] [PATCH] oe-buildenv-internal: Add UBOOT_CONFIG to environment whitelist

[Richard Purdie]

On Fri, 2013-10-04 at 19:22 -0300, Otavio Salvador wrote:
> The uboot-config class uses the UBOOT_CONFIG environment setting to
> choose which U-Boot option is intended to build. It is convenient to
> allow it to be set from the shell, as supported for MACHINE.
> 
> This allow, for example, to trigger a build as:
> 
> ,----
> | MACHINE=imx28evk UBOOT_CONFIG=nand bitbake core-image-minimal
> `----
> 
> Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>
> ---
>  scripts/oe-buildenv-internal | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

There are lots of things which we can expose from the shell, we only
really want to default to be things which are commonly changed though.
How often do people realistically change their uboot targets? I
appreciate that when working on uboot its useful but I don't think this
is a significant portion of the userbase?

Cheers,

Richard

> diff --git a/scripts/oe-buildenv-internal b/scripts/oe-buildenv-internal
> index bba6f8f..f8840c1 100755
> --- a/scripts/oe-buildenv-internal
> +++ b/scripts/oe-buildenv-internal
> @@ -106,4 +106,4 @@ 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 STAMPS_DIR"
> +SOCKS5_PASSWD SOCKS5_USER SCREENDIR STAMPS_DIR UBOOT_CONFIG"