|
From: | Dmitry Gutov |
Subject: | bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot |
Date: | Fri, 14 Apr 2023 19:04:20 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 |
On 14/04/2023 16:40, Eli Zaretskii wrote:
So on master if I upgrade all packages, ':core' packages would be automatically upgraded as well?is that what the default of that option means?I strongly object to that as a default; just because thereʼs a newer version on elpa of a :core package doesnʼt mean emacs should upgrade to it unless*explicitly* told to do so.I said we_can_ change the default; I didn't say we_must_. If enough people object to making that the default, it won't be changed.
We need to have a change in behavior that allows 'M-x package-install' to upgrade built-in packages. But that shouldn't automatically mean that package-menu-mark-upgrades marks all built-in packages for upgrade, or package-upgrade-all (nee package-update-all) does that either.
We could have another option that enables the latter to upgrade all built-ins too, of course.
Regarding the currently proposed user option, does it make sense to you to have such option that decides whether package-install upgrades built-ins? Whereas one can always upgrade a built-in package using 'i' (package-menu-mark-install) in the list-packages menu, no matter the value of that option. I get the backward-compatibility intent, but user options should also do something logical from a user's point of view.
[Prev in Thread] | Current Thread | [Next in Thread] |