bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot

[Eli Zaretskii]

> Date: Mon, 24 Apr 2023 00:53:30 +0300
> Cc: jporterbugs@gmail.com, philipk@posteo.net, 62720@debbugs.gnu.org,
>  joaotavora@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 23/04/2023 17:24, Eli Zaretskii wrote:
> >> Date: Sun, 23 Apr 2023 16:11:44 +0300
> >> Cc: jporterbugs@gmail.com, philipk@posteo.net, 62720@debbugs.gnu.org,
> >>   joaotavora@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca
> >> From: Dmitry Gutov <dmitry@gutov.dev>
> >>
> >>>> It addressed two last points from your previous email, obviously.
> >>> Which points are those?  Please help me identify them.
> >>
> >> These two:
> >>
> >>   > There is already such an option, added as part of fixing this bug.
> >>
> >> The binding was added, so now we straight away delegate to package-install.
> > 
> > I meant to give the user the control on whether package-update will
> > update built-in packages, like we did with package-install: either via
> > prefix argument or by customizing the user option.
> 
> That would be a different change, though.
> 
> So what are we guarding against here? That the user will choose a 
> built-in package to upgrade by accident?

Yes.  Also, against invocations of this command from other commands
and from the menu.

> And we'll show her an error, saying "use the prefix argument"?

No, I think we'll do whatever the code does today when passed a
built-in package.