On Tue, 2002-12-03 at 10:50, Stephen J. Turnbull wrote:
Do you use diff-mode? [...]
Yes, I do, but dunno if I made myself clear; I was kinda hoping that Ben
would commit the build-related stuff (ie. most of) from the patch :)
But not before Rendhalver gives his opinion:
Rendhalver, have you taken a look at this stuff, and do you want it held
until Sumos are rolled?
> + (2) To specifically set where the package hierarchies are
using
> + `configure', use the `--package-path' parameter, as follows:
Ville> [Just Doing It] Works for me,
Not in 21.5, it won't work in-place. XEmacs requires being told where
the package root is in that case.
Eek, another misunderstanding, I think (unless by "won't" you mean "in
the future"). I have this setup ("default staging" means the place
where "make install" dumps the packages by default):
~/cvs/xemacs/packages (contains the packages working dir)
~/cvs/xemacs/xemacs-packages (default staging for non-mule packages)
~/cvs/xemacs/mule-packages (default staging for mule packages)
...and then symlinks:
~/.xemacs/xemacs-packages -> ~/cvs/xemacs/xemacs-packages
~/.xemacs/mule-packages -> ~/cvs/xemacs/mule-packages
...and it works for me with 21.4 and 21.5 at the moment, and neither of
these have had any `--package-path' arguments to `configure'.
Anyway, the point is that it looks to me that one doesn't *have* to use
--package-path for the "personal installation" case. With the staging
vars pointing to ~/.xemacs/(xemacs|mule)-packages, it could Just Work.
There may be some load path shadows and warnings on startup, though.
--
\/ille Skyttä
scop at
xemacs.org