From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: master c622627: * Clean-up temporary eln test-suite directory when exiting (bug#48060)
Date: Wed, 28 Apr 2021 19:45:09 +0000 [thread overview]
Message-ID: <xjfo8dyyz0a.fsf@sdf.org> (raw)
In-Reply-To: <83y2d2dxel.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Apr 2021 22:25:22 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
>> Date: Wed, 28 Apr 2021 19:19:58 +0000
>>
>> > Andrea, is the problem with these directories specific to comp-tests,
>> > or does it happen in any test run in the native-compilation build?
>>
>> Every test might need to compile native code, not only directly invoking
>> `native-compile' & friends but also in case a trampoline has to be
>> synthesized.
>
> Then why don't these files end up in ~/.emacs.d/eln-cache/ ?
Because in the makefile we set HOME to the nonexisent directory so
~/.emacs.d/eln-cache/ is not reachable as it is computed relying on
`user-emacs-directory'.
> Or maybe we should have test/eln-cache/ and put the files there,
> without creating a new directory each time. Or even just deposit
> these files in the directory where the test runs, like we'd do with
> *.elc files.
>
> WDYT?
Of the two options I'd prefer the first so we don't have to modify the
mechanism to locate the eln files.
Andrea
next prev parent reply other threads:[~2021-04-28 19:45 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. [this message]
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
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=xjfo8dyyz0a.fsf@sdf.org \
--to=emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.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/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).