From: Ihor Radchenko <yantar92@posteo.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Philip Kaludercic <philipk@posteo.net>, 63800@debbugs.gnu.org
Subject: bug#63800: 30.0.50; [ELPA] Inaccurate installation instructions for built-in packages
Date: Thu, 15 Jun 2023 06:04:18 +0000 [thread overview]
Message-ID: <87r0qdxnvh.fsf@localhost> (raw)
In-Reply-To: <ee60fc2a-3c7d-094e-6a7b-3b5e6aacbd6b@gutov.dev>
Dmitry Gutov <dmitry@gutov.dev> writes:
>> Sure. But only in Emacs >=29 and it is not mentioned on the ELPA page.
>> For Emacs <29 ELPA instruction simply does not work - attempting to
>> follow it will just produce unhelpful message that package is already
>> installed.
>
> Is that a problem with the command or with the expectations?
>
> When Org is built-in, it *is* already installed, isn't it?
I have no problem with the command. I have problem with _ELPA page_
mentioning this command for built-in packages.
Org is always built-in. If a user goes to ELPA page, she most likely
wants to upgrade Org. And ELPA instructions do not tell how to do it.
Basically, what ELPA page for Org tells will not work for any common
Emacs version in the wild (and will not work for older Emacses that did
not ship with Org as well - they are not supported).
If you look into my other email, I suggested indicating on the ELPA
page when a package is built-in and also add instructions how to upgrade
it. That makes more sense _for ELPA page_.
This bug is not about `package-install'. This bug is about ELPA web page.
--
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-15 6:04 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
2023-06-15 2:08 ` Dmitry Gutov
2023-06-15 6:04 ` Ihor Radchenko [this message]
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=87r0qdxnvh.fsf@localhost \
--to=yantar92@posteo.net \
--cc=63800@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--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).