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
View this message in rfc822 format
Eli Zaretskii <eliz <at> gnu.org> writes:
>> Date: Fri, 5 May 2023 02:58:25 +0300
>> Cc: jporterbugs <at> gmail.com, philipk <at> posteo.net, 62720 <at> debbugs.gnu.org,
>> monnier <at> iro.umontreal.ca, larsi <at> gnus.org, joaotavora <at> gmail.com
>> From: Dmitry Gutov <dmitry <at> gutov.dev>
>>
>> Let's get back to the previous topic. What about the previous fix for
>> package-upgrade that I posted, one that makes it unconditionally upgrade
>> built-in packages when invoked?
>>
>> The one attached here: https://debbugs.gnu.org/62720#718
>>
>> Can we put it on master now, or do we have to wait for some feedback
>> from Emacs 29 first?
>
> I'd prefer the latter. I'd prefer even more to have same behavior in
> Emacs 20 and Emacs 30, which could be possible if we decide to make
> this change in Emacs 29.2, based on feedback. Because is it really a
> good idea to have the master and the release branch behave so
> differently in this regard? People who use both branches, or switch
> from one to the other, will become confused.
>
> Philip, Stefan: WDYT about this?
I am fine with any change, as long as package-upgrade-all does not
automatically switch from built-in packages to a different version from ELPA.
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.