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>
This commit is contained in:
Chris Larson 2010-12-14 08:10:36 -07:00 committed by Richard Purdie
parent 9260c08e1d
commit ea91b1dd87
1 changed files with 0 additions and 2 deletions

View File

@ -1,4 +1,3 @@
import os
import logging
import signal
import subprocess
@ -9,7 +8,6 @@ def subprocess_setup():
# Python installs a SIGPIPE handler by default. This is usually not what
# non-Python subprocesses expect.
signal.signal(signal.SIGPIPE, signal.SIG_DFL)
os.environ['PWD'] = os.getcwd()
class CmdError(RuntimeError):
def __init__(self, command):