On Wed 23 Aug 2006 at 02:27PM, Felix Schulte wrote:
> On 8/23/06, Dan Price <dp at eng.sun.com> wrote:
> >
> >I've been following this project, although I just joined the
> >mailing list.
> >
> >I have a couple of questions regarding the shape of the
> >project:
> >
> > - What is the nature of the replacing of libcmd.so? If I'm
> > not mistaken, I noticed that the existing libcmd.so is
> > being overwritten by the tarball which was recently
> > published. I wondered why that would be.
>
> All the functions in Solaris libcmd.so have been ported over to the
> ksh93 libcmd.so which will replace the Solaris version
Why are we intermingling "native" and "non native" code together
in one library? That seems like a suspiciously non-architectural
solution to a name collision. Is there a real rationale here?
It would seem to me to make a lot more sense to move the existing (in
Solaris) libcmd.so over to libcmd_private.so (or fold it into libuutil
or some such), and update the consumers. Since libcmd is undocumented
and private, this should be straightforward (although it might be
possible that there is some libcmd proliferation into JDS or CDE
or other places, which would be good to cleanse anyway).
> > - Which consolidation is this project targetting? I
> > understand that ksh93 has its own build system, and
> > I was wondering which consolidation would best accomodate
> > that uniqueness.
> ksh93 is integrated into the Opensolaris consolidation
[Alan's reply noted] Anyway, I assume you mean "OS/Net"? Or
do you mean SFW (which is, for example, where bash, tcsh and
zsh live).
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
