Re: [Bug: 21.4.18] site-lisp not in load-path
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
The second problem is "large complex packages". I
especially have
in mind JDEE and Emacspeak, whose upstream maintainers won't touch
the XEmacs packaging because the installed hierarchy is too
different from their idiosyncratic ways of doing things.
For crying out loud, it is not even possible to check the same
directory into two different CVS archives, even if the directory
layout matched that of the XEmacs package repository perfectly.
(42 JDE_DATA_GOES_HERE Make variables, anyone?) Perhaps AUCTeX,
too, but at least as of early 11.x it wasn't that big a deal to
force AUCTeX into an XEmacs installation.
I suggest that you either get a clue about AUCTeX by looking at it, or
refrain from commenting on its details. If it is not a big deal, what
are we to gather from the fact that it has taken years to find a
volunteer to do it, and that he needs several months on average to
synch, even though by now upstream generates complete packages?
Big deal or not, it does not appear to solicit people wanting to touch
any of it, so at least it is apparently a prohibitively high
psychological barrier.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum