From: Zhu Zihao <all_but_last@163.com>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to distribute dynamic modules by themselves?
Date: Mon, 21 Mar 2022 09:31:39 +0800 [thread overview]
Message-ID: <86h77sw0lh.fsf@163.com> (raw)
In-Reply-To: <951567BE-B2FA-4224-A369-B96469D2E083@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
IMO, You'd better to distribute the source code and let users compile it
by theirselves.
Yuan Fu <casouri@gmail.com> writes:
> I wrote a dynamic module that exposes a simple interface for Xapian, the
> indexing and searching engine. It could be very useful for indexing thousands of
> files and search in them. I use this module for my note-searching package.
>
> Normally people distribute their elisp package with supporting dynamic modules
> together, but in my case I want to distribute the dynamic module by itself,
> because indexing and searching is much more general than note-searching.
>
> Is there any way to put a dynamic module on ELPA so that other packages could use it conveniently?
>
> Yuan
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-03-21 1:31 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 [this message]
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
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=86h77sw0lh.fsf@163.com \
--to=all_but_last@163.com \
--cc=casouri@gmail.com \
--cc=emacs-devel@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.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).