Re: env (GNU coreutils) 5.93 patch

[Eric Blake]

>    [The bug-sh-utils list is obsolete, use bug-coreutils instead]
> 
> Would it be possible to make everything that goes to
> bug-{text,sh,files}-utils end up in bug-coreutils?  Or maybe it
> already does...

Yes, the three old lists already forward to bug-coreutils.  Often,
people posting to the old lists have an older version of the tools
installed, and need an upgrade; but since the original post was
about a patch to 5.93, it was just an indication that the poster
didn't pay close enough attention to the email address provided
by 'env --help'.

> 
>    When using /usr/bin/env as the interpreter in a #! line, you must
>    be sure that there is only one more word on the line, which means
>    that you cannot use env to invoke another program while still
>    providing arguments to that program.
> 
> Also, /usr/bin/env is a very non-standard place for env; it is usually
> located in /bin.  The best way to figureout where a program is, is to
> simply use a bit of sed magic, and have it output a new file which has
> the correct name of the program; and install that in whatever
> directory one keeps hacks in.

In fact, that is how coreutils 5.93 installs the groups(1) shell script.
Notice that the source code in the 5.93 tarball provides src/groups.sh,
then uses autoconf substitutions to create the actual groups utility
script from sed substitutions on groups.sh for installation using
parameters learned during configuration.

--
Eric Blake