On 06/20/2012 08:45 AM, Paul Eggert wrote: > More generally, the problem is that often people use scripts > in Perl or Python or whatnot to run a test, or run a test from > a shell spawned by a terminal emulator, and these scripts > or terminal emulators may execute chdir without updating PWD, > so the shell starts up with the wrong PWD.
POSIX requires the shell to sanitize PWD at startup rather than relying on the (possibly-incorrect) value that it may have inherited from the environment. But knowing whether a shell follows the POSIX rules on PWD could indeed be useful for deciding portable workarounds and/or altering the shell probing done at the front of autoconf scripts to pick a better shell. -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
