From: ams@gnu.org (Alfred M. Szmidt)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eggert@cs.ucla.edu, ulm@gentoo.org, yuri.v.khan@gmail.com,
eliz@gnu.org, emacs-devel@gnu.org, akrl@sdf.org
Subject: Re: Path for system-wide .eln files
Date: Sat, 05 Sep 2020 03:48:25 -0400 [thread overview]
Message-ID: <E1kESvx-0000RS-OR@fencepost.gnu.org> (raw)
In-Reply-To: <jwva6y5fcho.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 04 Sep 2020 17:42:45 -0400)
> The difference between the two directories is that the home directory
> may be shared between different architectures, while /usr/lib (or
> /usr/local/lib) is _not_ shared by its definition. Therefore the
> architecture makes sense in ~/.emacs.d/ but is redundant in /usr/lib/.
The extra info may be redundant but it does no harm.
If it is redundant, it also means that it doesn't have to be there.
But since there is no need to keep such information in libdir, it is
by definition for one specific architecture, it is better to remove
it.
There is also precedent in the GNU coding standards, e.g. most
anything under datarootdir, so it makes more sense to make libdir here
/usr/lib/emacs/VERSION as is the case with other things.
next prev parent reply other threads:[~2020-09-05 7:48 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 11:51 Native compilation: the bird-eye view Eli Zaretskii
2020-05-16 12:58 ` Andrea Corallo
2020-05-16 15:57 ` Paul Eggert
2020-05-16 16:26 ` Eli Zaretskii
2020-05-16 17:03 ` Andrea Corallo
2020-05-16 17:35 ` Eli Zaretskii
2020-05-16 17:44 ` Andrea Corallo
2020-05-16 17:50 ` Eli Zaretskii
2020-05-16 18:26 ` Andrea Corallo
2020-05-16 18:32 ` Eli Zaretskii
2020-05-16 18:41 ` Andrea Corallo
2020-05-18 14:27 ` Andrea Corallo
2020-05-19 5:08 ` ASSI
2020-05-19 16:25 ` Andrea Corallo
2020-05-19 16:37 ` Stefan Kangas
2020-05-19 19:16 ` Andrea Corallo
2020-05-29 17:25 ` Andrea Corallo
2020-06-02 15:16 ` Stefan Monnier
2020-06-03 14:23 ` Andrea Corallo
2020-06-03 14:38 ` Stefan Monnier
2020-08-10 9:23 ` Andrea Corallo via Emacs development discussions.
2020-08-10 12:20 ` Stefan Monnier
2020-08-10 21:34 ` Andrea Corallo via Emacs development discussions.
2020-08-15 10:51 ` Andrea Corallo via Emacs development discussions.
2020-08-15 15:00 ` Eli Zaretskii
2020-08-19 15:01 ` Andrea Corallo via Emacs development discussions.
2020-08-20 0:53 ` tumashu
2020-08-20 8:11 ` Andrea Corallo via Emacs development discussions.
2020-08-23 12:19 ` Andrea Corallo via Emacs development discussions.
2020-08-23 15:37 ` Stefan Monnier
2020-08-23 16:31 ` Andrea Corallo via Emacs development discussions.
2020-08-23 18:20 ` Stefan Monnier
2020-08-24 8:03 ` Andrea Corallo via Emacs development discussions.
2020-08-24 13:31 ` Stefan Monnier
2020-08-24 14:09 ` Andrea Corallo via Emacs development discussions.
2020-08-30 10:18 ` Path for system-wide .eln files (was: Native compilation: the bird-eye view) Ulrich Mueller
2020-08-30 20:50 ` Path for system-wide .eln files Andrea Corallo via Emacs development discussions.
2020-08-30 21:51 ` Stefan Monnier
2020-08-31 19:13 ` Andrea Corallo via Emacs development discussions.
2020-08-31 21:16 ` Ulrich Mueller
2020-09-01 4:28 ` Yuri Khan
2020-09-01 7:16 ` Ulrich Mueller
2020-09-01 8:46 ` tomas
2020-09-04 17:55 ` Andrea Corallo via Emacs development discussions.
2020-09-04 18:25 ` Ulrich Mueller
2020-09-04 19:47 ` Andrea Corallo via Emacs development discussions.
2020-09-04 20:01 ` Ulrich Mueller
2020-09-04 21:42 ` Stefan Monnier
2020-09-04 22:59 ` Ulrich Mueller
2020-09-05 2:58 ` Stefan Monnier
2020-09-05 7:10 ` Ulrich Mueller
2020-09-06 6:24 ` Andrea Corallo via Emacs development discussions.
2020-09-05 7:48 ` Alfred M. Szmidt [this message]
2020-05-16 19:11 ` Native compilation: the bird-eye view Yuan Fu
2020-05-17 4:04 ` Ihor Radchenko
2020-05-17 11:18 ` Arthur Miller
2020-05-16 22:09 ` John Wiegley
2020-05-17 4:11 ` Ihor Radchenko
2020-05-17 7:43 ` 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=E1kESvx-0000RS-OR@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=akrl@sdf.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ulm@gentoo.org \
--cc=yuri.v.khan@gmail.com \
/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).