emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Eli Zaretskii
Subject: Re: emacs-29 9b775ddc057 1/2: ; * etc/EGLOT-NEWS: Fix wording of last change.
Date: Mon, 08 May 2023 14:24:25 +0300

> Date: Sun, 7 May 2023 23:36:24 +0300
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 07/05/2023 22:32, Eli Zaretskii wrote:
> > Packages to install: 23 (xref-1.6.3 verilog-mode-2022.12.18.181110314 
> > use-package-2.4.5 tramp-2.6.0.4 svg-1.1 soap-client-3.2.1 so-long-1.1.2 
> > python-0.28 project-0.9.8 org-9.6.5 ntlm-2.1.0 nadvice-0.4 map-3.3.1 
> > let-alist-1.0.6 jsonrpc-1.0.17 flymake-1.3.4 external-completion-0.1 
> > erc-5.5 eldoc-1.14.0 eglot-1.15 cl-lib-0.7.1 cl-generic-0.3 
> > bind-key-2.4.1).  Packages to upgrade: 2 (editorconfig-0.9.1 
> > inspector-0.29).  Proceed? (y or n)
> 
> At least nadvice, cl-lib and cl-generic seem to be the odd ones (the 
> built-in versions are higher, and the ELPA packages are supposed to be 
> used as shims or backward compatibility wrappers). That looks like a bug.

Yes, I think it's an unrelated bug.  We had already reports about
strange status values, and there's a new bug#63064 today about similar
problems.  We should try to fix this for Emacs 29, I think.

> Regarding potential downsides in general:
> 
> - We simply increase the odds of breakage when a built-in package is 
> upgraded because it will reach more people, across different Emacs 
> versions. There is good and bad in that (features will reach them faster 
> too), but it's something to consider.
> 
> - I very rarely use Tramp or Org. I don't use ERC or bind-key. Or 
> so-long, python, ntlm, use-package, verilog-mode. Unlike other installed 
> packages (which I have hand-picked), these packages are here just by the 
> virtue of being included in Emacs, but flipping the pref will also cause 
> them to be upgraded (downloaded, take time unarchiving, take up space) 
> every time there is a new version out. It's nothing dangerous 
> (probably), but seems unfortunate anyway.

AFAIU, the "U" command is not for everyone.  There are alternatives
which allow selective upgrades, and users who don't want "surprises",
or want the upgrade to take as little time and disk space as possible,
should use those alternatives instead of "U".  I'll try to make that
clear in the documentation.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]