From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gnu-emacs@gentoo.org, emacs-devel@gnu.org
Subject: Re: Where should dynamic modules be installed?
Date: Mon, 21 Oct 2019 16:44:48 +0300 [thread overview]
Message-ID: <83d0eq2oxb.fsf@gnu.org> (raw)
In-Reply-To: <w6gtv8274y9.fsf@kph.uni-mainz.de> (message from Ulrich Mueller on Mon, 21 Oct 2019 12:45:02 +0200)
> From: Ulrich Mueller <ulm@gentoo.org>
> Date: Mon, 21 Oct 2019 12:45:02 +0200
> Cc: gnu-emacs@gentoo.org
>
> We are going to include the first package with a dynamically loaded
> module (emacs-libvterm) in Gentoo. The question arose where the .so file
> should be installed? Since it is a system dependent binary, installing
> it under /usr/share/emacs/ looks wrong. I cannot find anything about a
> recommended install location in the documentation.
Why do you think /usr/share/emacs/ is wrong? That's where the
site-lisp directory lives.
> Also, wouldn't it be cleaner if Emacs had a separate variable (analog to
> image-load-path, custom-theme-load-path, etc.) for loading of dynamic
> modules, instead of reusing load-path?
The idea with reusing load-path was that modules will almost always be
accompanied by some .el file(s), and having those separately from the
module binaries would be a complication.
next prev parent reply other threads:[~2019-10-21 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 10:45 Where should dynamic modules be installed? Ulrich Mueller
2019-10-21 13:44 ` Eli Zaretskii [this message]
2019-10-21 14:36 ` Ulrich Mueller
2019-10-24 0:31 ` Paul Eggert
2019-10-24 12:02 ` Andy Moreton
2019-10-24 14:28 ` Stefan Monnier
2019-10-24 14:04 ` Eli Zaretskii
2019-10-24 15:39 ` Ulrich Mueller
[not found] <mailman.96.1571932821.13349.emacs-devel@gnu.org>
2019-10-24 16:24 ` Ulrich Mueller
2019-10-24 18:36 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d0eq2oxb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gnu-emacs@gentoo.org \
--cc=ulm@gentoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.