unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: tgbugs@gmail.com, 43475-done@debbugs.gnu.org,
	Andrea Corallo <akrl@sdf.org>
Subject: bug#43475: feature/native-comp; add a site-lisp path to comp-eln-load-path
Date: Mon, 05 Jun 2023 04:54:10 -0400	[thread overview]
Message-ID: <yp1legycmrx.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <ur1qy2hyz@gentoo.org> (Ulrich Mueller's message of "Sat, 19 Sep 2020 12:12:20 +0200")

Ulrich Mueller <ulm@gentoo.org> writes:

>>>>>> On Fri, 18 Sep 2020, Andrea Corallo wrote:
>
>> Tom Gillespie <tgbugs@gmail.com> writes:
>
>>> 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 think ${libdir}/emacs/site-lisp/native-lisp would be probably more
>> future proof but I've no strong preference.
>
>> Ulrich what would be your suggestion for this?
>
> I'd prefer the shorter path. I believe it's very unlikely that there
> could be other files in future that would be both lisp and architecture
> dependent, i.e. that would be installed in ${libdir}/emacs/site-lisp/
> as well. In other words, the additional subdirectory level would be
> totally redundant.
>
> So, my suggestion would be either ${libdir}/emacs/site-lisp/ or
> ${libdir}/emacs/site-eln/ with a slight preference for the second.
>
> (Note that Gentoo would create another subdirectory when installing an
> add-on elisp package, so the path would be (for example)
> ${libdir}/emacs/site-eln/${package_name}/.)

Closing this very old bug still related to feature/native-comp as I
think ATM the interface we provide satisfies distro needs.  Happy to
reopen if more work is needed in this area.

Best Regards

  Andrea





      reply	other threads:[~2023-06-05  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 17:37 bug#43475: feature/native-comp; add a site-lisp path to comp-eln-load-path Tom Gillespie
2020-09-18 19:09 ` 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 [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=yp1legycmrx.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=43475-done@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=tgbugs@gmail.com \
    --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).