GNU bug report logs -
#62720
29.0.60; Not easy at all to upgrade :core packages like Eglot
Previous Next
Reported by: João Távora <joaotavora <at> gmail.com>
Date: Fri, 7 Apr 2023 22:11:01 UTC
Severity: normal
Found in version 29.0.60
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #712 received at 62720 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 22 Apr 2023 15:14:01 +0300
> Cc: jporterbugs <at> gmail.com, philipk <at> posteo.net, 62720 <at> debbugs.gnu.org,
> joaotavora <at> gmail.com, larsi <at> gnus.org, monnier <at> iro.umontreal.ca
> From: Dmitry Gutov <dmitry <at> gutov.dev>
>
> On 22/04/2023 15:00, Eli Zaretskii wrote:
> >> Also think forward to Emacs 30: I think the most reasonable choice would
> >> be to have package-update upgrade builtins by default, whereas
> >> package-update-all and package-menu-mark-for-upgrades probably still
> >> need to be preffed off (not sure, but we won't be able to make the
> >> choice until later, I think).
> > I don't see why package-update and package-update-all should behave
> > differently wrt core packages. If the user expresses his/her will to
> > update core packages, then package-update-all should do this for all
> > of them.
>
> The idea is that if the user invokes 'M-x package-update' interactively
> and inputs the name of the package, they express their intention to
> update said package this way. Whether it's core or not.
>
> With package-update-all or package-menu-mark-for-update, the user does
> not have a chance to specify which of the core packages they want to
> upgrade, if any.
That's why we should have both the prefix-arg and the user option: one
is for one-off update of a single package, the other for updating many
of them. It's the same logic as for package-install in those cases.
This bug report was last modified 2 years and 17 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.