From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Unable to install from elpa
Date: Mon, 29 May 2023 21:50:48 +0700 [thread overview]
Message-ID: <u52e4a$dao$1@ciao.gmane.io> (raw)
In-Reply-To: <878rdbwlf3.fsf@localhost>
On 26/05/2023 15:23, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> I have realized that the command is specified in the README.org file, so
>> it is mentioned twice on https://elpa.gnu.org/packages/org.html
>
>> However prior to Emacs-29.1 built-in packages are filtered-out from
>> completion list and ignored by non-interactive command
>> ...
>> Should `list-packages' recipe be used in the README.org file instead?
>
> The first instance of M-x package-install <RET> org <RET> comes from
> ELPA itself. Considering that ELPA is targeting various Emacs versions,
> it should probably be corrected there first.
Generally agree, but I am skeptical concerning changes in ELPA since
only minority of packages are affected.
> The second instance in README.org may then be altered according to what
> ELPA devs do.
Users may open README.org outside of ELPA. "To install a more recent
version..." is is not enough even for coming Emacs-29 since the default
value for `package-install-upgrade-built-in' is nil.
Another pitfall with install instruction in an .org file is that if the
file is opened in Emacs < 29 then package.el generates mixed-versions
.elc files. A precaution is necessary that `list-packages' should be run
in a clean emacs session, not the one with README.org.
next prev parent reply other threads:[~2023-05-29 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 5:39 Unable to install from elpa Carlos Pita
2021-11-13 6:11 ` Carlos Pita
2023-05-25 15:30 ` Max Nikulin
2023-05-26 8:23 ` Ihor Radchenko
2023-05-29 14:50 ` Max Nikulin [this message]
2023-05-30 8:10 ` Ihor Radchenko
2023-12-22 11:26 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='u52e4a$dao$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).