Re: emacs-29 9b775ddc057 1/2: ; * etc/EGLOT-NEWS: Fix wording of last change.

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 6 May 2023 13:46:26 +0300
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 06/05/2023 13:35, Eli Zaretskii wrote:
> >> Date: Sat, 6 May 2023 13:14:32 +0300
> >> From: Dmitry Gutov<dmitry@gutov.dev>
> >>
> >> On 06/05/2023 09:44, Eli Zaretskii wrote:
> >>> +using the more general command 'package-install', which by default
> >>> +will not upgrade "built-in" packages, those that come with Emacs.
> >> Friendly reminder: while 'M-x package-install' does not upgrade
> >> "built-in" packages "by default", it doesn't upgrade any other packages
> >> at all, ever.
> > Really? so what does package-install do?
> 
> 'M-x package-install' installs a package if it's not already installed.
> 
> >> I'd hate to create an impression in some users that 'package-install' is
> >> a suitable instrument to upgrade packages.
> > It isn't? then what is it for?
> 
> See above.
> 
> It also _can_ install a newer version of the package if the first 
> argument is of type 'package-desc', but that's basically an internal 
> overload, not something that can be user interactively, or easily in the 
> init script. BTW, the value of package-install-upgrade-built-in has no 
> effect on that "overload".

I'm surprised, to say the least.  To recap:

  . the entire discussion of bug#62720, of which this is fallout, was
    about allowing package-install to upgrade Eglot, and according to
    João, that's what package-install did before Emacs 29.  Was this
    all based on a mistake? if so, why no one has said so in all that
    long argument??
  . the text I changed also talks about package-install, and yet you
    didn't object to it, why?

So please forgive me if I don't quite believe my eyes when I read your
messages in this matter.