Martin Bochnig wrote: > SUNWxorg-cfg: > At first I had the Xorg-versions of libXaw (for use by xorgcfg) inside > SUNWxorg-clientlibs. > However, recently I noticed the redundance, because the entries were > also present in SUNWxorg-cfg already. So I went ahead and commented out > the corresponding entries in SUNWxorg-clientlibs's prototype file. Beng, > for some reason (probably wrong or missing !search directive in > SUNWxorg-cfg's prototype), SUNWxorg-cfg does not properly install them. > So they would be missing on a target host.
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. > 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 -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering
