GNU bug report logs - #63800
30.0.50; [ELPA] Inaccurate installation instructions for built-in packages

Previous Next

Full log

View this message in rfc822 format

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 63800 <at> debbugs.gnu.org
Subject: bug#63800: M-x package-install, upgrading, and dealing with :core packages (was: [elpa] elpa-admin 1d766451f8: Suggest `package-install' to install packages (bug#63800))
Date: Thu, 13 Jul 2023 17:26:39 +0000

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

>> AFAIU, one of the problems is that already installed packages do not
>> even show up in the completion and one cannot enter
>> M-x package-install <RET> org <RET>. The last <RET> will only trigger
>> completion window where org is not listed at all.
>>
>> But wasn't this discussed in the past? There was quite a lengthy
>> discussion about this in the past (I did not quite follow it until the
>> end).
>
> Indeed, but I think the discussion did not take a step back to think
> about what the UI should be in a more general sense (IIRC it was
> focused on "what should we do right now for `emacs-29`").

Then, M-x package-install may (1) Remove REQUIRE-MATCH from its
interactive `completing-read' call. (2) If the package is built-in and
:core on ELPA, ask to run package upgrade (y/n) - something like
"Package foo is already installed. New version is available on ELPA. Upgrade? (y/n)"
(3) Fall back to user-error that package is not found otherwise.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.