From: Eli Zaretskii <eliz@gnu.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: emacs-devel@gnu.org
Subject: Re: Dedicated search path variable for architecture-dependant loadable file
Date: Fri, 15 Jan 2021 13:34:23 +0200 [thread overview]
Message-ID: <83zh1aa0xs.fsf@gnu.org> (raw)
In-Reply-To: <86h7niwjl0.fsf@163.com> (message from Zhu Zihao on Fri, 15 Jan 2021 19:00:43 +0800)
> From: Zhu Zihao <all_but_last@163.com>
> Date: Fri, 15 Jan 2021 19:00:43 +0800
>
> It's OK for me. But it's not an idiomatic way in distribution packaging.
> For distrbution packaged Elisp packages, Lisp files usually placed at
> <prefix>/share/emacs/site-lisp. In FHS spec
> (https://www.pathname.com/fhs/pub/fhs-2.3.html), <prefix>/share should
> only contains architecture-independant files, and obviously dynamic
> library is not the case. They should be placed under <prefix>/lib.
>
> My suggestion is add a new `native-load-path` Lisp variable and
> `EMACSNATIVELOADPATH` environment variable to enable a dedicated search
> path for native files.
So you are saying that the Lisp part of a module should be installed
under /usr/share/emacs/site-list, and it's shared-library part under
/usr/lib? Wouldn't this complicate things?
I'm not sure I understand the problem: doesn't a module normally come
with a Lisp interface file? And if so, couldn't the module solve this
inside the Lisp part, e.g., load the shared-library file explicitly?
IOW, why do we need to treat this situation specially?
Failing that, how about arranging for architecture-dependent
subdirectories under site-lisp instead?
prev parent reply other threads:[~2021-01-15 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 11:00 Dedicated search path variable for architecture-dependant loadable file Zhu Zihao
2021-01-15 11:34 ` Eli Zaretskii [this message]
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=83zh1aa0xs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=all_but_last@163.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).