Martin Buchholz <martin(a)xemacs.org> writes:
Users can always override /usr/dt contents using --site-libraries
and
--site-includes.
Why? If /usr/dt, by your own writings contains X11 libraries and
usually, but not always only Motif and/or CDE, why the hell doesn't
--x-includes and --x-libraries override it? Has the meaning of X
changed?
If I tell configure that I don't want any stinking CDE/Motif by
an unfortunately large number of options, then what business does it
have sticking that directory ahead of others that I have explicitly
asked to be put ahead via --x-includes and --x-libraries. Excuse me,
but configure is clearly broken in this area.
Users are also free to `rm -rf /usr/dt' and XEmacs will build
just
fine with just the vendor-supplied X in /usr/openwin. But most
users will choose not to shoot themselves in the foot this way.
A brilliant suggestion.
Does anyone actually have a real live PROBLEM that removing /usr/dt
would solve? There would certainly be many problems that it would
introduce.
Yes. I couldn't build an XEmacs binary on HP/UX against /usr/contrib
X11R6 libraries without manually modifying configure to make /usr/dt
go away.
I have that patch sitting in my incoming queue. I'm almost in enough
of a foul mood over this to consider applying it.