From: Tom Gillespie <tgbugs@gmail.com>
To: 43475@debbugs.gnu.org, akrl@sdf.org
Cc: ulm@gentoo.org
Subject: bug#43475: feature/native-comp; add a site-lisp path to comp-eln-load-path
Date: Thu, 17 Sep 2020 13:37:04 -0400 [thread overview]
Message-ID: <CA+G3_PPwWP0Y-S-5jJHFoHMb2QbFAaoTopK8_NbfrdLC_cChAQ@mail.gmail.com> (raw)
Hi Andrea,
Sorry for the delay getting this submitted. Here is a summary of the
discussion about how to handle the site-lisp equivalent for eln files. Best!
Tom
Use case. We need a default convention for where eln files compile from
files in /usr/share/emacs/site-lisp can be installed by a package manager.
For the record, https://github.com/gentoo/gentoo/pull/16962 was the start
of these discussions and the following devel thread is also relevant
https://lists.gnu.org/archive/html/emacs-devel/2020-08/msg01036.html.
My suggestion to use /usr/share was incorrect as Ulrich points out since
/usr/share should never contain arch specific files. Thus, ${libdir}
is the right base.
Suggestions from the previous discussion are /usr/lib{,64}/emacs/site-eln and
/usr/lib{,64}/emacs/site-lisp/eln.
If we want to mirror the way native-lisp is used for the system files
then ${libdir}/emacs/site-lisp and ${libdir}/emacs/site-lisp/native-lisp
are two other options.
I'm not sure the intervening native-lisp folder is necessary,
especially given that
there is the additional folder that is present for each version, and
since the fact
that we are in ${libdir}/emacs automatically suggests that we are dealing with
native arch specific files. However, I suppose that there might be some future
case where something other than the native-lisp files would be included in
${libdir}/emacs, so separating the eln files in their own folder would
help. I have
no idea how likely that happening in the future is though.
next reply other threads:[~2020-09-17 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 17:37 Tom Gillespie [this message]
2020-09-18 19:09 ` bug#43475: feature/native-comp; add a site-lisp path to comp-eln-load-path Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-19 10:12 ` Ulrich Mueller
2023-06-05 8:54 ` Andrea Corallo
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=CA+G3_PPwWP0Y-S-5jJHFoHMb2QbFAaoTopK8_NbfrdLC_cChAQ@mail.gmail.com \
--to=tgbugs@gmail.com \
--cc=43475@debbugs.gnu.org \
--cc=akrl@sdf.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 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).