all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36443@debbugs.gnu.org
Subject: bug#36443: Canonicalized build directory name in container leads to confusion (was guix build mixes build dirs?)
Date: Thu, 04 Jul 2019 09:59:47 +0200	[thread overview]
Message-ID: <87imsi9qmk.fsf@gnu.org> (raw)
In-Reply-To: <A7319B78-0D30-42D8-B398-E016E1FB75F8@vllmrt.net> (Robert Vollmert's message of "Tue, 2 Jul 2019 15:41:00 +0200")

Hi,

Robert Vollmert <rob@vllmrt.net> skribis:

>> On 2. Jul 2019, at 15:37, Ludovic Courtès <ludo@gnu.org> wrote:
>> 
>>>     /* In a sandbox, for determinism, always use the same temporary
>>>        directory. */
>>> -    tmpDirInSandbox = useChroot ? canonPath("/tmp", true) + "/guix-build-" + drvName + "-0" : tmpDir;
>>> +    tmpDirInSandbox = useChroot ? canonPath("/tmp", true) + "/guix-build-" + drvName : tmpDir;
>> 
>> The result would be that the temporary directory would always have a
>> different name inside and outside the container.  Consequently,
>> debugging along the lines of what the manual suggests (info "(guix)
>> Debugging Build Failures") would become pretty much impossible.
>
> Why do you think it would become impossible?

“Impossible” is an exaggeration, but when you source the
‘environment-variables’ file, for example, PWD and other variables will
refer to /tmp/guix-build-….drv, which won’t exist.  Likewise, generated
files such as Makefiles would have captured the ….drv name.

Like Mark writes, it’s not the end of the world: you can simply rename
/tmp/guix-build-….drv-0 to /tmp/guix-build-….drv.  However, it means
that things would be inconvenient by default, which doesn’t sound great
to me.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2019-07-04  8:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-30 10:24 bug#36443: guix build mixes build dirs? Robert Vollmert
2019-06-30 12:13 ` bug#36443: suspicion Robert Vollmert
2019-06-30 17:18 ` bug#36443: guix build mixes build dirs? Mark H Weaver
2019-06-30 17:22   ` Robert Vollmert
2019-06-30 17:43     ` bug#36443: Canonicalized build directory name in container leads to confusion (was guix build mixes build dirs?) Mark H Weaver
2019-06-30 17:47       ` Robert Vollmert
2019-06-30 17:59         ` Mark H Weaver
2019-07-02 13:37           ` Ludovic Courtès
2019-07-02 13:41             ` Robert Vollmert
2019-07-04  7:59               ` Ludovic Courtès [this message]
2019-07-04  8:04                 ` Robert Vollmert
2019-07-04 15:12                   ` Ludovic Courtès
2019-07-03  3:48             ` Mark H Weaver
2019-06-30 17:30   ` bug#36443: guix build mixes build dirs? Mark H Weaver

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87imsi9qmk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36443@debbugs.gnu.org \
    --cc=rob@vllmrt.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.