From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Where should dynamic modules be installed?
Date: Thu, 24 Oct 2019 10:28:59 -0400 [thread overview]
Message-ID: <jwvimoei5o4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <vz1blu6qrl9.fsf@gmail.com> (Andy Moreton's message of "Thu, 24 Oct 2019 13:02:26 +0100")
>> I expect that the main reason Emacs doesn't have a variable like
>> module-directory now, is that packagers haven't yet encountered the
>> Emacs module system (it has been off by default, though that will change in
>> Emacs 27) and so haven't run into problems like the one you mention.
>
> Indeed.
Not only that, but also sharing filesystems between different machines
has been rather rare with current cheap large disks, so storing
architecture-specific files alongside architecture-agnostic files hasn't
been problematic in practice. Maybe instead of looking for <foo>.so
we should be looking for <foo>.<arch>.so to make it easy to share
a directory between machines of different architectures?
If Debian doesn't want to put those architecture-specific files into
/usr/share/emacs/site-lisp, then it can tweak the `load-path` to include
/usr/lib/<arch>/emacs/site-modules or something like that.
Stefan
next prev parent reply other threads:[~2019-10-24 14:28 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
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 [this message]
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
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=jwvimoei5o4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=andrewjmoreton@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).