On Sat, Sep 23, 2006 at 08:49:02PM -0700, John Plocher wrote: > $BIN/../lib/libcmd.so.x:b_<...> > The entry points in the above libcmd shared object. > They is used by ksh, ast and a bunch of /usr/bin/cmd > wrappers, and is intended to be used by others.
That's the crux then, isn't it? If libcmd is intended to be dlopen()ed by unnamed third parties and its b_xxx() entry points are intended to be called by them, then this is intended to be a public interface, and the shared object name and path are significant. If, OTOH, it's intended to be used *only* by ksh93 and those 40 or so /bin commands that are implemented by libcmd, then it can be private and its name/path can be changed by this project. So, which is it? If public, then the ARC pretty much has to butt out on this, no? If private then the ARC can reasonably request a shared object name change. Nico --
