POSIX UPU command issues

[Jeff Johnson]

+++ This bug was initially created as a clone of Bug #2192 +++

the LSB spec doesn't seem to specify the albeit POSIX "command" command. Is
that intentional?

+++

Some comments in the original bug should not be dropped even though the
basic work is complete - command and type will appear in LSB 4.0.

This is the comment:

The published POSIX page for command lists -v and -V under UPU (User
Portability Utilities), which are described as optional via the POSIX
wording, and the LSB wording says that "at least" the mandatory behavior
is required. We could say the UPU behavior is required as well for
command, but we'd have to update the intro text to do so - the current
implementation does not allow built-in utilities to follow the same
"difference-to-POSIX" model that external utilities, and interfaces,
follow. So we need a resolution to that dilemma in one of several ways,
here are the ones that currently come to mind:

- extend mkcmdtable to recognize (guiding) Standard = LSB, Reference
Specification = POSIX for builtins
- set the Standard to the next POSIX version, where the UPU-marked stuff has
become mandatory
- add some wording that says that UPU-marked stuff in SUSv3 is required (may
have impacts on other utilities which may or may not lead to other changes)
- include wording in the section intro that just calls out command as needing
to support this extra bit

Additionally, the internal naming of the rolled-up commands section should
probably be renamed (to "commands"?) to avoid possible conflict/confusion
with the command named "command".