Re: Enhancement request: SUS bootstrapping procedure for shell scripts

[Philip Guenther <guenther@xxxxxxxxx>]

On Wed, Aug 5, 2009 at 5:28 PM, Wayne Pollock<pollock@acm.org> wrote:
...
> To have this guaranteed to work under a POSIX shell you
> need one further change:  getconf should behave as if it
> were a built-in utility in a POSIX shell.

Isn't this requirement already met by the 'command' command, such that
given a shell that conforms to POSIX (SUS, etc), you can get a PATH
that will give utilities that conform to that standard using:
        PATH=$(command -p getconf PATH)     # optional: suffix that
with ":$PATH"

?  I think the only issue unresolved is just "how can a shell script
be portable written so that (the bulk of) it runs with a
POSIX-compliant shell?"


Philip Guenther