Re: Why not include all ELPA packages in an Emacs release?

[Stefan Kangas <stefankangas@gmail.com>]

Eli Zaretskii <eliz@gnu.org> writes:

> What we discussed was the desire to move packages out of core in a way
> that a release tarball would include those package.  That is what we
> have a consensus about (but not a complete and satisfactory solution
> yet).

It's possible that we have interpreted the previous discussions a bit
differently, or that I'm filling in too many blanks.

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.

> Back to the suggestion in this thread: I cannot really see why would
> we want to add almost 500 packages to Emacs.  Especially since AFAIR
> some of them solve the same or very similar problems in different,
> sometimes even contradictory, ways.
>
> If there are packages on ELPA which we consider to be a must for users
> (I don't think there are, but maybe I'm forgetting something), lets
> add them to core instead.

Not sure if there are any that are a must, but I do think a few of them
would be good to have included.  For example, `json-mode` would be nice
to have available OOTB (though we now have `json-ts-mode` too).