From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, michael.albinus@gmx.de
Subject: Re: master c622627: * Clean-up temporary eln test-suite directory when exiting (bug#48060)
Date: Thu, 29 Apr 2021 14:41:47 +0000 [thread overview]
Message-ID: <xjfczudxidw.fsf@sdf.org> (raw)
In-Reply-To: <83h7jpe94q.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Apr 2021 12:24:21 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, michael.albinus@gmx.de
>> Date: Thu, 29 Apr 2021 08:29:17 +0000
>>
>> That said this could help in the file clean-up side of the problem, but
>> IIUC the complain of this thread is the dependency Makefile ->
>> stratup.el.
>
> With that preferred solution, startup.el will not need to be changed,
> will it?
>
>> Than the real question is how should Emacs understand that is being used
>> for a testsuite run so it can use "test/eln-cache/" without any
>> dependency Makefile -> Emacs?
>
> I'm not sure what dependency you are talking about. What I had in
> mind was to arrange in test/Makefile.in to use that directory for
> *.eln files, via some Lisp variable or environment variable. This
> way, Emacs will not need to understand it is being run as part of the
> test suite.
Answering both your questions: Emacs will have to understand that in
this condition "test/eln-cache/" has to be pushed to
`comp-eln-load-path'. To do this as you suggest we could set an
env-var, but this is not much different from what we do now (and IIUC
this is what Michael doesn't like much and was called a dependency).
Also we'd still have to handle this push in startup.el, am I wrong?
Maybe we could have the Emacs invocation in the Makefile changed to
explicitly tweak `comp-eln-load-path' using -eval?
Regards
Andrea
next prev parent reply other threads:[~2021-04-29 14:41 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. [this message]
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=xjfczudxidw.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).