Re: please don't add incompatibilities

"D. J. Bernstein" <[email protected]> wrote:
> Until that happens, creating yet another emacs fork, with yet another
> site-lisp location, is only going to make the situation worse. The
> advantages of having files in /package are outweighed by the costs of
> having an even messier site-lisp access system for the foreseeable
> future.

I'm not convinced.  The situation is better for the admin who is
installing multiple versions, upgrading, downgrading, etc.  It's worse
for programs that need to find the site-lisp directory.  Which are
those?  There's Emacs itself - but it always knows where its own
installed site-lisp directory is.  There are also installers for elisp
packages.  But the way I do things, they get installed as separate
packages anyway; they have their own site-lisp directory, and they
don't need to know where Emacs's site-lisp directory was created.  I
had to add some code to my .emacs to find all other packages'
site-lisp directories and add them to load-path, but that was easy
enough to write.


paul