On Friday 23 October 2009 16:33:01 Eric Blake wrote: > Eric Blake <ebb9 <at> byu.net> writes: > > Is 'env -i -u a=b' really supposed to output a=b, or should it be an > > error (because a=b is not a valid environment name)? Right now, it is > > the former, because we are using putenv() to remove variables from > > environ, rather than unsetenv(). Similarly, should env -u '' issue an > > error? > > Also, if I'm reading POSIX correctly, > > env -- a=b true > > is supposed to execute true with a=b in the environment, rather than GNU > behavior of executing ./a=b (POSIX says to use 'env ./a=b true' to get > similar behavior).
eh ? my installed coreutils-7.6 (as well as a quick test of 8.0) does the right thing according to POSIX -- it sets "a" to "b" and executes `true`. > Do we go ahead and call this a bug, and fix it? Or is it obscure enough to > wrap in POSIXLY_CORRECT? i dont think this is obscure. setting env vars are not options. -mike
signature.asc
Description: This is a digitally signed message part.
