|Subject:||bug#14513: Fwd: bug#14513: 24.3.50; Site load-path pieces differ in MSYS build|
|Date:||Thu, 30 May 2013 20:49:40 +0100|
[Why private email?]
> Date: Thu, 30 May 2013 20:14:35 +0100
> From: Richard Copley <address@hidden>
> > > c:\>dir /B c:\emacsYour site-lisp won't, but the one in ROOT/share/emacs will.
> > > emacs-111818
> > > emacs-112125
> > > emacs-112416
> > > site-lisp
> > You can still have separate directories like that, unless I'm missing
> > something. The directory structure below emacs-NNNNNN directories
> > will be different, but that's all.
> Also the site-lisp directory will not be on the load-path.
Then why do you need separate trees? That's the only reason why you
> I'm not actively using more than one build.
need the site-lisp outside of the Emacs tree.
Use the Posix-standard
structure and one root for all the Emacs installations, and the
problem is gone, because you have the common site-lisp directory in
You mean, you will never uninstall? Then why do you keep the versions
> > The new structure has advantages which I described in that mail in> > March.Well, maybe I'm the only one who works on so many platforms.
> (1) You're the first one I know about who thinks that's important.
> (2) is wrong.
It's not wrong as long as you keep all the installations under the
same root, like /usr/local on Unix.
> (3) I don't follow. Other platforms, really?Yes. Imagine that your --prefix is on a networked volume that can be
accessed from Windows and Unix systems alike. Then only the
architecture-dependent files (binaries) need to be separate;
everything under %emacs_dir%/share/emacs/ can be installed only once
and used by Emacs from any OS.
|[Prev in Thread]||Current Thread||[Next in Thread]|