On Wed, Jul 14, 2010 at 06:31:53PM -0700, Chris Larson wrote:
>Is there some reason you couldn't just ensure all the proxy variables are in
>the env whitelist, so they end up in the metadata? This patch seems
>extremely hackish to me.
duh. I was setting BB_ENV_EXTRAWHITE in bitbake.conf instead of environ,
sorry for the noise.
what was bb.msg functions fn argument supposed to do, btw?
In order to really see which env vars were cleaned out i had to
diff --git a/lib/bb/utils.py b/lib/bb/utils.py
index c0cc9c6..7ab412c 100644
--- a/lib/bb/utils.py
+++ b/lib/bb/utils.py
@@ -476,7 +476,7 @@ def filter_environment(good_vars):
del os.environ[key]
if len(removed_vars):
- bb.msg.debug(1, bb.msg.domain.Util, "Removed the following
variables from the environment:", ",".join(removed_vars))
+ bb.msg.debug(1, bb.msg.domain.Util, "Removed the following
variables from the environment: %s" % (",".join(removed_vars)))
return removed_vars
_______________________________________________
Bitbake-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bitbake-dev
