Alan Coopersmith wrote: > The libXaw in SUNWxorg-cfg was intended as a private library for use only > by xorgcfg until such time as we were ready to replace the public > libXaw in > /usr/openwin/lib with a new /usr/X11/lib/libXaw.so - I've not had time to > investigate the differences between the two libXaw's or determine if any > binary compatibility will be broken, and since such a small amount of > software uses libXaw these days, it never seemed like that high a > priority.
Certainly, last week I saw your comments in the pkgdefs. However, binary compatibility seems to be broken. I experimented with LD_PRELOAD'ing Sun's version of libXaw, lofs-mounting one version over the other and vice versa, etc. > >> Yes, but there is one issue: /usr/openwin/lib is expected to be >> present, and to be populated with (un-re-distributable?) legacy >> libraries. So for the distros we depend on a *self*-hosted FOX, as >> Moinak has pointed out over a month ago. So for Indiana, BeleniX, >> SchilliX, Nextenda, MartUX && Co. we might need our own version of >> gdm. But those openwin/lib related questions are a topic for for >> themselves ... > > Which is why Moinak has worked with Laca from the JDS team to do a JDS > build that only relies on the open packages Moinak built (which are > labeled > as "FOX" packages though they aren't from our project gate and only > Moinak > knows what's really in them - hopefully he'll fix that soon). > > http://mail.opensolaris.org/pipermail/jds-review/2007-September/001811.html > > Awesome! My approach had been more simplistic: Simply removing the Nevada X pkgs. %martin
