From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Yuan Fu <casouri@gmail.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: How to distribute dynamic modules by themselves?
Date: Wed, 23 Mar 2022 18:16:43 -0400 [thread overview]
Message-ID: <jwvils4gw16.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y210apam.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 23 Mar 2022 12:20:17 +0100")
Lars Ingebrigtsen [2022-03-23 12:20:17] wrote:
> Yuan Fu <casouri@gmail.com> writes:
>> Is there any way to put a dynamic module on ELPA so that other
>> packages could use it conveniently?
> I'm not quite sure what the state of dynamic modules on ELPA is.
> Stefan?
Currently, there's only one such module,m i.e. `pq`.
It's not well integrated yet.
The way it's supposed to work (after Someone™ codes it up) is that
during `package-install` a chunk of ELisp in the attempts to compile
the module.
Then the same chunk of ELisp should (re)compile the module as/when
needed when the ELisp package is loaded. Ideally, this is done from
a function, so it's not done when the package is barely loaded but when
that function is actually called (which is a more convincing evidence
that the module is needed).
Regarding distributing pre-compiled modules, there's currently no
infrastructure for that. We could consider it, but it can only be
a partial solution (we can't easily make sure we cover all possible
architecures, ...), so the focus for now is in getting the
automated/lazy-compilation working.
Stefan
next prev parent reply other threads:[~2022-03-23 22:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 23:51 How to distribute dynamic modules by themselves? Yuan Fu
2022-03-21 1:31 ` Zhu Zihao
2022-03-22 5:07 ` Richard Stallman
2022-03-22 8:44 ` Zhu Zihao
2022-03-23 3:55 ` Richard Stallman
2022-03-23 19:44 ` Yuan Fu
2022-03-25 3:29 ` Richard Stallman
2022-03-23 11:20 ` Lars Ingebrigtsen
2022-03-23 19:48 ` Yuan Fu
2022-03-25 3:29 ` Richard Stallman
2022-03-25 5:53 ` Yuan Fu
2022-03-27 5:27 ` Richard Stallman
2022-03-27 5:27 ` Richard Stallman
2022-03-23 22:16 ` Stefan Monnier [this message]
2022-03-23 22:30 ` Ergus
2022-03-24 3:19 ` Richard Stallman
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=jwvils4gw16.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.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).