Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>> "Jens" == Jens Lautenbacher
<jens(a)tellux.de> writes:
Jens> Sorry if this is a faq or plain stupid, but
I simply seem to
Jens> be unable to get an xemacs-21 beta working...
I'm not all that surprised; the install process is in flux,
big-time
right now, especially with respect to packages.
Hopefully things will be slowing down now. The mechanics of it all
are working quite well based on the testing I've been doing of it.
Jens> After a long time I want to again work a bit with xemacs,
Jens> and so I decided to get a new package enabled xemacs-21. I
Jens> downloadded the cvs xemacs-20 and xemacs-packages.
CVS'ing packages is the hard way. Download the `binary' tarballs from
the FTP site for a first installation. Figure out where your packages
should be ($prefix/lib/xemacs/packages, $prefix/lib/xemacs/mule-packages)
and untar the packages you want there.
If you're running in place, put the installed package directories
anywhere (`packages' and `mule-packages' if you do Mule), and make
symbolic links to them in the top level source directory.
OK. You don't need to get the source if you would rather just
install
the binaries. In fact, it is not possible to build a Mule XEmacs at
present without an installed mule-base package AFAIK.
That is correct. There's information about the bootstrap process in
etc/BETA and etc/PACKAGES.
I suspect that nearly all of the downloads of released 21.0 will use
the prepackaged SUMO versions[1] of Lisp packages
xemacs-packages-21.0.tar.gz and mule-packages-21.0.tar.gz.
Footnotes:
[1] No, they don't exist now, but they will for 'net release.