Re: Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?]

[Eli Zaretskii <eliz@gnu.org>]

> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: Stefan Kangas <stefankangas@gmail.com>,  emacs-devel@gnu.org,
>   monnier@iro.umontreal.ca,  philipk@posteo.net
> Date: Fri, 07 Jun 2024 22:48:25 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> My understanding was that this was always going to be something like
> >> 1) make it possible to ship ELPA packages with core Emacs and then
> >> 2) decide which packages should be included.
> >> 
> >> To my mind, step 2 could either be restricted to only include packages
> >> that used to be in core, or it could not be.  The difference is not very
> >> big, at least not in principle, since before we bundle even two
> >> packages, we still have to solve the issue of how to bundle even one.
> >
> > Sure, but we never meant that step 2 will include all of ELPA, I
> > think.  And at least my understanding of step 2 was indeed that it
> > should allow to have more core packages on ELPA than to add packages
> > to the Emacs release tarballs.
> 
> What is a good core package to start working on migrating to ELPA?

We never seriously discussed that, since the issues with doing that
are not yet resolved, so any such work would be premature at best.

But the obvious candidates are those that are already on ELPA: Org,
Eglot, Tramp, and a few others.  With those, the only aspects of
"work" to remove them from emacs.git are those which currently prevent
such a move to begin with.