From: Philip Kaludercic <philipk@posteo.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Ihor Radchenko <yantar92@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 15:35:48 +0000 [thread overview]
Message-ID: <87v8foagbv.fsf@posteo.net> (raw)
In-Reply-To: <12eb3b7e-f944-6a96-cfb9-285891d659ca@gutov.dev> (Dmitry Gutov's message of "Thu, 15 Jun 2023 15:34:09 +0300")
Dmitry Gutov <dmitry@gutov.dev> writes:
> On 15/06/2023 09:04, Ihor Radchenko wrote:
>> I have no problem with the command. I have problem with_ELPA page_
>> mentioning this command for built-in packages.
>
> Cool.
>
>> 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_.
>
> Not a bad idea, though it will also require adding some metadata on
> when the package was added to Emacs.
>
> Perhaps a simpler alternative is to stop referencing 'package-install'
> and instead point uses to 'M-x list-packages'.
I think this would be better as well. A lot of users don't even know
what version they use, so we should have to describe how to find that
out as well. And if that isn't enough, we would also have to explain
what core, built-in and ELPA packages are, and how they interact. Not
worth it, IMO.
next prev parent reply other threads:[~2023-06-15 15:35 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
2023-06-15 12:34 ` Dmitry Gutov
2023-06-15 15:35 ` Philip Kaludercic [this message]
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=87v8foagbv.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=63800@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=yantar92@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).