Darryl Okahata writes:
Jonathan Harris <jhar(a)tardis.ed.ac.uk> wrote:
> A sensible install tree for XEmacs on mswindows might look like:
>
> PROGS\XEmacs\
> packages\
> XEmacs-21.0\
> bin
> info
> lisp
>
> where PROGS should default to "C:\Program Files".
What's the philosophy for packages? A scheme such as the
above
works only if packages are independent of XEmacs versions. However, in
practice, I have not found this to be true; packages tend to depend on a
particular XEmacs version or vice-versa.
Actually, this is not the case at all. Packages are generally
forward-compatible with XEmacs.
For example, I currently build and run a full 21.0 with no packages at
all. All the packages come from using 20.4 as my "package".
I would say that I am a power user, I use the XEmacs functionality to
the full extent of the law, and I don't miss anything.
Anyway, I would say that I am a person who believes in a package
directory separate from the version, the same way that site-lisp (now
obsolete) is on a separate path.
--
Colin