Re: Adding use-package to core

[Eli Zaretskii <eliz@gnu.org>]

> From: Philip Kaludercic <philipk@posteo.net>
> Cc: Sean Whitton <spwhitton@spwhitton.name>,  luangruo@yahoo.com,
>   emacs-devel@gnu.org,  xenodasein@tutanota.de
> Date: Fri, 18 Nov 2022 20:43:33 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Sean Whitton <spwhitton@spwhitton.name>
> >> Cc: xenodasein--- via "Emacs development discussions."
> >>  <emacs-devel@gnu.org>,  eliz@gnu.org,  xenodasein@tutanota.de
> >> Date: Fri, 18 Nov 2022 12:29:25 -0700
> >> 
> >> Hello,
> >> 
> >> On Mon 14 Nov 2022 at 08:27AM +08, Po Lu wrote:
> >> 
> >> > Personally, I hope that everything most people find useful will
> >> > eventually make its way into Emacs, because doing so is a direct
> >> > shortcut to making Emacs more useful for everyone.
> >> 
> >> We are still aiming to bundle all of GNU ELPA with releases of Emacs at
> >> some point, right?
> >
> > Not all of it, no.  Only some of it.
> 
> What would the criteria for inclusion be like?

Packages that we'd like to have in Emacs, but for some reason are on
ELPA instead.  This would allow packages like Magit, Org, project.el,
and maybe others to stay only on ELPA.  Which is why including in a
release packages from ELPA is something we'd like to be able to do in
the first place.

ELPA admits packages that do the same job as other packages, and also
packages that do some jobs that are extremely niche jobs.  So
including everything makes very little sense to me.