Re: decision on moving core packages to ELPA; also move to obsolete?

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>,  daniele@grinta.net,  emacs-devel@gnu.org
> Date: Tue, 15 Dec 2020 14:57:41 -0500
> 
> >> Doesn't package.el install stuff under ~/.emacs.d/elpa/ ?
> > yes.
> >> > If so, what happens with installed Lisp files under /usr/share/ ?
> > They stay there, but ~/.emacs.d/elpa is earlier in load-path.
> 
> Not only that: we could very easily setup the bundled packages such that
> they are only added to `load-path` by `package-activate`, so if a newer
> version is in ~/.emacs.d/elpa the bundled version won't even make it to
> the `load-path` (contrary to what happens with the packages hosted in
> Core like `python.el` or Org).

So now we are talking about changing the basic logic in
normal-top-level-add-subdirs-to-load-path and
normal-top-level-add-to-load-path?  And maybe in subdirs.el as well?
We can, of course, do any or all of those, but we do need a
comprehensive picture of what needs to be done and how this stuff will
work when done, in all the relevant use cases.  What we have now is a
long list of issues and a longer list of ideas how to solve them.
Like I said, a lot of loose ends that needs to be tied.

We are not ready.  Not yet.