From: Ihor Radchenko <yantar92@posteo.net>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 63800@debbugs.gnu.org
Subject: bug#63800: 30.0.50; [ELPA] Inaccurate installation instructions for built-in packages
Date: Thu, 08 Jun 2023 11:01:12 +0000 [thread overview]
Message-ID: <8735322p6v.fsf@localhost> (raw)
In-Reply-To: <87mt1bks75.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
>>> You probably want to set `package-install-upgrade-built-in' to non-nil,
>>> or use the package menu to install packages.
>>
>> Sure. But only in Emacs >=29 and it is not mentioned on the ELPA page.
>
> I am not a fan of the option to begin with, and wouldn't want to
> advertise it. The official way of switching from built-in packages to
> ELPA should still be to use the package menu.
I will not argue about this. This bug report merely raises the issue
with current installation instructions. You are in a better position to
recommend one or another way to install/upgrade core packages from ELPA.
>> For Emacs <29 ELPA instruction simply does not work - attempting to
>> follow it will just produce unhelpful message that package is already
>> installed.
>
> So what would you suggest changing?
I suggest changing
To install this package, run in Emacs:
M-x package-install RET <package-name> RET
to something like
This package is a part of Emacs since Emacs XX.X.
To install the package in Emacs <XX.X, run:
M-x package-install RET <package-name
To update the built-in package version in Emacs >=XX.X to ELPA version:
<instructions to install the package that actually work>
--
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>
next prev parent reply other threads:[~2023-06-08 11:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 8:05 bug#63800: 30.0.50; [ELPA] Inaccurate installation instructions for built-in packages Ihor Radchenko
2023-05-31 6:46 ` Philip Kaludercic
2023-05-31 6:59 ` Ihor Radchenko
2023-06-07 19:06 ` Philip Kaludercic
2023-06-08 11:01 ` Ihor Radchenko [this message]
2023-06-15 2:08 ` Dmitry Gutov
2023-06-15 6:04 ` Ihor Radchenko
2023-06-15 12:34 ` Dmitry Gutov
2023-06-15 15:35 ` Philip Kaludercic
2023-06-15 20:56 ` Ihor Radchenko
2023-07-09 11:59 ` Ihor Radchenko
2023-07-10 2:14 ` Dmitry Gutov
2023-07-12 7:46 ` Philip Kaludercic
2023-07-12 16:24 ` Ihor Radchenko
2023-07-12 16:38 ` Philip Kaludercic
2023-07-13 9:39 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735322p6v.fsf@localhost \
--to=yantar92@posteo.net \
--cc=63800@debbugs.gnu.org \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).