James Carlson wrote:
[snip]
> Why wouldn't this scan a ksh93-specific location first, such as a
> /usr/lib/ksh93/ directory? You could have your own libcmd.so{,.1}
> buried in there, encourage others to deliver plugin libraries to that
> separate directory, and there'd be no conflict.
libcmd is not ksh93-specific (to be exact: It's AST's libcmd, not
ksh93's libcmd).
For example some of the AST applications use it and those commands which
reside in libcmd have wrappers in AST's /usr/bin which call directly
into libcmd (and we're already having patches around to do the same for
Solaris since some of the commands have superiour functionality and/or
POSIX-conformance than those commands in the Solaris codebase and it's a
very low-hanging fruit to do a switch).
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
