>>>>> "w" == warly <[EMAIL PROTECTED]> writes:
>> Is it /wise/ to fork Xemacs incompatibly with it's own package
>> manager?
w> I guess it must not and it must be fixed, but it seems that on
w> some point xemacs ignore the configure option giving the
w> datadir as /usr/share and still use /usr/lib/
Symlinks seem to work fine as a temporary measure; I merged the
Mandrake i386 tree with the /usr/lib/xemacs tree and then moved
xemacs-packages to become i386-Mandrake-linux and symlinked that as
/usr/lib/xemacs/xemacs-packages ... yes it violates your architecture
rule, but if at such time we get XEmacs to agree to that rule, the
groundwork is ready for the switch.
Is there /really/ architecture-dependent code in those files? I
hadn't though that possible with elisp, but I suppose it's probably
true.
--
Gary Lawrence Murphy - [EMAIL PROTECTED] - TeleDynamics Communications
- blog: http://www.auracom.com/~teledyn - biz: http://teledyn.com/ -
"Computers are useless. They can only give you answers." (Picasso)
