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

[Eli Zaretskii]

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Jeremy Bryant <jb@jeremybryant.net>,  stefankangas@gmail.com,
>   emacs-devel@gnu.org,  monnier@iro.umontreal.ca,  philipk@posteo.net
> Date: Sat, 08 Jun 2024 10:10:31 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> One aspect are regression tests. Tramp has ca 100 test cases in
> tramp-tests.el. I don't know whether they run out-of-the-box with the
> Tramp ELPA package. And it would be a big miss if they won't run by the
> regular "make check" of Emacs. These regression tests are an infinite
> source of indications, what is still missing to be fixed in Tramp.

Does this mean Tramp on the master branch of elpa.git and Tramp on the
master branch of emacs.git are different?  If not, then why don't you
know whether Tramp on ELPA succeeds in the tests that Tramp in Emacs
does?

Anyway, what to do with tests of a core package that is on ELPA is an
interesting question.  I guess the tests should also be moved out of
emacs.git to ELPA, and should be brought/updated into the tree when
the package is updated?