From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Mekeor Melire <mekeor@posteo.de>, 63987@debbugs.gnu.org
Subject: [bug#63987] Should jinx-mod.so be installed into /.../lib or into /.../share/emacs/site-lisp/...?
Date: Wed, 21 Jun 2023 06:23:30 +0200 [thread overview]
Message-ID: <e4b9d2ab272b44bf82e6c4cd5b97bdcd5e271cea.camel@gmail.com> (raw)
In-Reply-To: <874jn1bwxu.fsf@posteo.de>
Am Dienstag, dem 20.06.2023 um 22:04 +0000 schrieb Mekeor Melire:
> Daniel Mendler says: "My suggestion is that you put the library
> file [jinx-mod.so] in some appropriate directory, which must be on
> the load-path. I assume that there exists some convention on Guix on
> where to install native modules."
> https://github.com/minad/jinx/issues/86#issuecomment-1597221252
>
> And I think they are right. We should have a convention about where
> to install native modules (.so-files) and add that directory to
> Emacs' load-path.
>
> One approach would be to use $out/lib/emacs (or a new subdirectory of
> it). E.g. we would install jinx-mod.so into that path and Guix would
> add it to the EMACSLOADPATH environment-variable. (Currently, Guix
> only makes use of .../lib/emacs/native-site-lisp which is added to
> EMACSNATIVELOADPATH environment-variable.)
What's the functional difference between EMACSLOADPATH and
EMACSNATIVELOADPATH here? Why would the latter not work?
> Another approach would be to agree on installing *.so-files into
> $out/share/site-lisp/PACKAGE-VERSION/ so that it is already present
> Emacs' load-path as is.
>
> What do you think?
/lib/emacs/native-site-lisp sounds like the wrong place regardless, as
does /share/site-lisp. Perhaps /lib/emacs/site-mod?
Cheers
next prev parent reply other threads:[~2023-06-21 4:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 23:00 [bug#63987] [PATCH] gnu: Add emacs-jinx mekeor
2023-06-18 11:34 ` [bug#63987] Should jinx-mod.so be installed into /.../lib or into /.../share/emacs/site-lisp/...? Mekeor Melire
2023-06-18 11:56 ` Liliana Marie Prikler
2023-06-20 22:04 ` Mekeor Melire
2023-06-21 4:23 ` Liliana Marie Prikler [this message]
2023-06-18 12:14 ` [bug#63987] [PATCH] gnu: Add emacs-jinx Liliana Marie Prikler
2023-06-18 23:02 ` [bug#63987] [PATCH v2] " Mekeor Melire
2023-06-18 23:17 ` [bug#63987] [PATCH v3] " Mekeor Melire
2023-09-09 10:30 ` bug#63987: " Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4b9d2ab272b44bf82e6c4cd5b97bdcd5e271cea.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=63987@debbugs.gnu.org \
--cc=mekeor@posteo.de \
/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/guix.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).