> From: Roland Mainz <roland.mainz at nrubsig.org> ... > Umpf. Please read last months discussion in the ksh93-integration > archive. We had a flamewar (which nearly caused the destruction of this > project (and I am unhappy that we revisit this horror again... ;-( )), a > long discussion and even a phone conference about the libcmd issue.
Such fun! > To describe it short words (April did some research on this and may be > able to give you more details): Both ksh93 and Solaris have a libcmd. To > ensure backwards-compatibility with both versions we're shipping a > "merged" version which contains both functionalities. This should be the > most painless solution for both sides and doesn't cause any problems for > it's consumers since all functions from the ksh93 version of libcmd > start with |b_*()| (for builtin command, see the builtin(1) manual page) > while the Solaris libcmd functions start with |def*()|. I *think* all the functions in Solaris's libcmd are Consolidation Private (or at least Private of some form). By the submission, I'd have to assume all the functions in ksh93's libcmd are Project Private, although there is some indication that the intent may be to raise that at a later date. Hence, we could rename both of these and still be well within any interface commitments. I think renaming at least one of these might be a better solution than merging them. Its kinda amusing to have this particular name conflict. As a survivor of the AT&T/Sun marrage and subsequent divorce of the late 80's and early 90's, we would view both of these libraries as "it came from New Jersey". 8^) - jek3
