Re: elisp-packages, mule and non-mule?
|--==> "ML" == Mats Lidell <matsl(a)contactor.se> writes:
ML> Hi,
ML> I've been thinking of trying out 'with-mule' in parallel with the
ML> standard beta non-mule build I'm using. Is that possible? Would I need
ML> two different sets of the elisp packages (with and without) or is it
ML> possible to use a non-mule XEmacs with elisp packages build with a
ML> MULE XEmacs?
You shouldn't run into problems. Mule packages get installed into
their own tree (/usr/local/lib/xemacs/mule-packages/) and a non-Mule
XEmacs doesn't put that directory into the load-path.
I have 6 different XEmacsen in parallel here (a Mule & non-Mule of
each of 21.[145]) all using the same set of packages. The way I do it
is to:
- Install my everyday "production" XEmacs in the normal
default place (/usr/local) and install all the packages I
want in the normal default place.
- For the extra XEmacsen I './configure --prefix=/other/dir'.
'make', and then 'make install'.
- Finally make a symlink from the installed packages tree to
$prefix/lib/xemacs
ln -s /usr/local/lib/xemacs $prefix/lib/xemacs
Works great. The hard part is when you have half a dozen different
XEmacsen all running simultaneously, remembering what you are doing in
each one. :-)
Oh, and BTW, if you have ever installed an XEmacs package using the
XEmacs package tools or from downloading from the FTP site, you are
using packages built with a Mule XEmacs.
ML> Somewhat related: (Curious) What is the rational in supporting both
ML> versions. Why not just support with mule?
Probably because when Mule was first implemented it was as buggy as
hell and as slow as your grandmother. I don't think that's the case
now, and the work that Ben is currently doing is probably a prelude to
a Mule-only XEmacs.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|