unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: rgm@gnu.org, monnier@iro.umontreal.ca, 48141@debbugs.gnu.org
Subject: bug#48141: 28.0.50; Files left over by native compiler
Date: Mon, 03 May 2021 14:49:53 +0300	[thread overview]
Message-ID: <83bl9s6nq6.fsf@gnu.org> (raw)
In-Reply-To: <a4dfe72ae2811489989c@heytings.org> (message from Gregory Heytings on Mon, 03 May 2021 08:42:08 +0000)

> Date: Mon, 03 May 2021 08:42:08 +0000
> From: Gregory Heytings <gregory@heytings.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 48141@debbugs.gnu.org
> 
> Given that requirement (atomicity) and its implication (same partition), 
> would it not be better to create these temporary files in a 'tmp' 
> subdirectory of their target directory (e.g. 'lisp/tmp' for el files in 
> 'lisp' and 'lisp/calc/tmp' for el files in 'lisp/calc') instead of using 
> random filenames in the target directory itself?

Since they will be in the tree anyway, why does it matter in what
subdirectory they will be deposited?

Using a subdirectory has a disadvantage: you need to create it and
delete it, which can hamper atomicity, and also cause trouble in
parallel builds.  So if the advantage is unclear, I'd rather not go
there.

There's nothing wrong with what we do now, IMO.  We arrived at that
after several iterations, which did try some of the suggestions in
this thread.  If Magit users are annoyed by their popping up
unexpectedly, adding them to .gitignore is TRT and will solve the
issue cleanly and safely.





  reply	other threads:[~2021-05-03 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 14:36 bug#48141: 28.0.50; Files left over by native compiler Stefan Monnier
2021-05-01 14:44 ` Eli Zaretskii
2021-05-01 16:54 ` Glenn Morris
2021-05-02  7:05   ` Lars Ingebrigtsen
2021-05-03  8:42   ` Gregory Heytings
2021-05-03 11:49     ` Eli Zaretskii [this message]
2021-05-03 12:11       ` Gregory Heytings

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=83bl9s6nq6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=48141@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@gnu.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).