diff options
author | Chris Larson <chris_larson@mentor.com> | 2010-12-14 08:10:36 -0700 |
---|---|---|
committer | Richard Purdie <rpurdie@linux.intel.com> | 2011-01-04 14:46:50 +0000 |
commit | ea91b1dd878a5c726ee5118b98c4987fa0a994e7 (patch) | |
tree | 49e32258da6c0cfd7bc589b2a34585d10c1ed725 /meta/recipes-support/beecrypt | |
parent | 9260c08e1d4d2cf62639a77e8ca28ef0f30ab4be (diff) | |
download | openembedded-core-ea91b1dd878a5c726ee5118b98c4987fa0a994e7.tar.gz openembedded-core-ea91b1dd878a5c726ee5118b98c4987fa0a994e7.tar.bz2 openembedded-core-ea91b1dd878a5c726ee5118b98c4987fa0a994e7.tar.xz openembedded-core-ea91b1dd878a5c726ee5118b98c4987fa0a994e7.zip |
Fix PWD issue with new exec_func_shell
The previous attempt was incorrect. The issue isn't that subprocess fails to
set PWD, it's that PWD is in the metadata, inherited from the environment, and
is re-exported, overwriting the actual accurate one in the shell environment
with the old one from the metadata. So, ensure that PWD in the metadata is
not exported.
We can ditch this when the environment handling is reworked (e.g. poky's
commit to do so).
(Bitbake rev: 2c8683234acf514706b2b69f5b29405485e664dd)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'meta/recipes-support/beecrypt')
0 files changed, 0 insertions, 0 deletions