I. Szczesniak writes:
> On 9/22/06, Joseph Kowalski <Joseph.Kowalski at eng.sun.com> wrote:
> >
> > Thanks for the explanation, but the reason I'm inquiring is to determine
> > if the name libcmd is significant.
>
> The name libcmd is significant because it is a library which can be
> referenced using
> builtin -f cmd commandname
> to load one of the commands located in libcmd.
> The name 'cmd' is a well known location to find those commands for
> dynamically linked versions of ksh93. Renaming the library will break
> existing scripts like our and this is not acceptable.
Ah, ok, thanks for the explanation.
If it *did* need to be renamed, would there be a barrier to having an
alias? Just have the "-f <x>" handler compare the string against
"cmd" and use an alternate name for that one case. (Not pretty, I
know, but doesn't seem to pose any obvious problems.)
A better alternative might be to look at the places scanned. It
doesn't seem to make sense to me that 'builtin -f' would resolve
against /usr/lib, at least first in the list. I sure don't want
'builtin -f ipmp' to load the IPMP library into the shell; there's
nothing useful there.
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.
--
James Carlson, KISS Network <james.d.carlson at sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
