From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@gmail.com>
Cc: akrl@sdf.org, michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: master c622627: * Clean-up temporary eln test-suite directory when exiting (bug#48060)
Date: Fri, 30 Apr 2021 08:09:31 +0300 [thread overview]
Message-ID: <83im44cq9g.fsf@gnu.org> (raw)
In-Reply-To: <CAO2hHWZaGqRmoPmV5fZKJo8CGORGLVOyrtKefVovVkMaOOtxKg@mail.gmail.com> (message from chad on Thu, 29 Apr 2021 13:47:18 -0700)
> From: chad <yandros@gmail.com>
> Date: Thu, 29 Apr 2021 13:47:18 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>, EMACS development team <emacs-devel@gnu.org>, Andrea Corallo <akrl@sdf.org>
>
> At the risk of opening a can of worms... Would it make sense to have emacs look for an eln directory
> underneath dirs given to $EMACSLOADPATH/--directory?
No, because *.elc files are platform-independent, whereas *.eln files
are platform-dependent. It is conceptually incorrect to put them in
the same directory, and also against the Posix tree rules.
> From my naive vantage, I would usually want that, and I have a hard time thinking of non-convoluted situations
> where I would want them to be separate, EXCEPT for the platform-(in)dependent file system issue, which
> doesn't seem like a concern for the test suite.
First, this is a concern for test suite as well. And besides, what
you suggest is a general feature, not something for the test suite
alone, AFAIU.
next prev parent reply other threads:[~2021-04-30 5:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210427213426.6174.29110@vcs0.savannah.gnu.org>
[not found] ` <20210427213427.8318C20D0F@vcs0.savannah.gnu.org>
2021-04-28 11:30 ` master c622627: * Clean-up temporary eln test-suite directory when exiting (bug#48060) Michael Albinus
2021-04-28 12:12 ` Eli Zaretskii
2021-04-28 19:19 ` Andrea Corallo via Emacs development discussions.
2021-04-28 19:25 ` Eli Zaretskii
2021-04-28 19:45 ` Andrea Corallo via Emacs development discussions.
2021-04-29 5:20 ` Eli Zaretskii
2021-04-29 8:20 ` Andrea Corallo via Emacs development discussions.
2021-04-29 8:29 ` Andrea Corallo via Emacs development discussions.
2021-04-29 9:24 ` Eli Zaretskii
2021-04-29 14:41 ` Andrea Corallo via Emacs development discussions.
2021-04-29 15:11 ` Eli Zaretskii
2021-04-29 15:26 ` Michael Albinus
2021-04-29 15:47 ` Eli Zaretskii
2021-04-29 20:47 ` chad
2021-04-30 5:09 ` Eli Zaretskii [this message]
2021-04-29 9:21 ` Eli Zaretskii
2021-04-28 19:30 ` Michael Albinus
2021-04-28 19:47 ` Andrea Corallo via Emacs development discussions.
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=83im44cq9g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=yandros@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).