john s jacobs anderson <jacobs(a)azstarnet.com> writes:
a draft version is available at
<
URL:http://www.xemacs.org/Install/index.html>
please test it out (i.e., pretend you know nothing and try to install
based just on what's on that page).
I am afraid I don't have the time to that right how, but here is the
result from a critical read,
also, *BSD/Solaris/other non-RedHat platforms: where do these
instructions break on your setup?
[Personally the most difficult part here would be to make sure you
have all the additional libraries and making sure XEmacs will find them]
1. [Get ] xemacs-21.1.*.tar.gz, xemacs-21.1.*-elc.tar.gz,
xemacs-21.1.*-info.tar.gz
Why don't just put xemacs-21.1.*.tar.gz? The rest will build automatically.
2.Expand the above files into the directory used for compiling, e.g.
tar zxvf xemacs-*.tar.gz -C /usr/src/.
This assumes GNU tar.
10.From the menubar, choose Options -> Manage Packages ->
Update
Installed Packages. This will download the most recent package index
(PGP errors may
occur and can be ignored) and list the packages available for
install. Instructions and key bindings for this buffer are at the
bottom; use the scroll bar to view them.
If you have a scrollbar, you most likely also have a (popup) menu
where all the bindings are listed. Additionally C-h m works just like
in any other mode.
If
in doubt about a particular package, it is generally safe to just
install it.
I think this is wrong (at least using the automated tools), you should
never install a mule package. Package-*.el do know how to separate out
Mule related packages but unfortunately this only works on a Mule
XEmacs (thus if you run both you should use the Mule version to
install packages).
Generally would like some lines like
X. At this point it is good to read README.packages
I know people won't read docs but I sure don't want the website to
advocate that. I would say it needs at least a link to the true
release notes.
Jan