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

[Dmitry Gutov <dmitry@gutov.dev>]

On 06/05/2023 22:38, Eli Zaretskii wrote:
>> Date: Sat, 6 May 2023 22:14:13 +0300
>> Cc: emacs-devel@gnu.org
>> From: Dmitry Gutov <dmitry@gutov.dev>
>>
>>> What about installation from the list-packages menu: will it upgrade a
>>> built-in package if package-install-upgrade-built-in is non-nil?
>>
>> Installation or upgrade?
>>
>> package-menu-mark-upgrades ('U') is not affected by
>> package-install-upgrade-built-in. It won't.
> 
> Shouldn't it?

Maybe, maybe not.

A user that customized that option to have (package-install 'eglot) 
ensure that a version from ELPA is installed might not want or expect 
for it to affect package-menu-mark-upgrades and/or package-upgrade-all. 
Or anticipate the full consequences anyway.

After all, in the former case you choose a specific package to install, 
and the last two act on all built-ins together.

>> But a version from ELPA can still be installed by using 'i' in the
>> list-packages menu. Just as we've written in the docstrings.
> 
> That was stated at the very beginning of bug#62720.

Just making sure we're on the same page.

>>> If package-upgrade was not in Emacs 28, how did users upgrade
>>> installed packages in Emacs 28 and before?
>>
>> Using package-menu-mark-upgrades ('U').
> 
> So we should allow that, at least as an optional behavior in Emacs 29,
> right?

I don't believe in "optionality" here.

If the user has to hunt for the option to toggle, they might as well 
find the "one little trick" that does the thing they want.

Most people will only have to do that once (per config), if at all: 
after Eglot is upgraded this way, it's smooth sailing from then on.

>> We should probably focus on getting Emacs 29 out soon
> 
> Why do you think this is not what happens?

I'm just saying we've spent enough time on this particular issue. We can 
improve the docs the best we can and move on.