unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36443-done@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 17:12:32 +0200	[thread overview]
Message-ID: <87bly93kbj.fsf@gnu.org> (raw)
In-Reply-To: <4AFAEC1B-9ECA-4A26-BD9F-23B6A31D73CE@vllmrt.net> (Robert Vollmert's message of "Thu, 4 Jul 2019 10:04:13 +0200")

Hello,

Robert Vollmert <rob@vllmrt.net> skribis:

>> On 4. Jul 2019, at 09:59, Ludovic Courtès <ludo@gnu.org> wrote:
>> 
>> Hi,
>> 
>> “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.
>
> But, wait, won’t they refer to /tmp/guix-build-0.drv? So debugging a build
> from /tmp/guix-build-1.drv will use a mix of both directories?

As the manual explains, the name inside the container is fixed, it’s
always .drv-0; the name outside may vary to avoid naming collisions or
as a consequence of setting TMPDIR.

>> 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?
>
> I don't particularly care anymore. I think it’s a confusing mess, but for
> myself I’ve learnt this wart and won’t run into the problem anymore.

I understand this has been a confusing experience, but I can’t really
think of any other sensible way to approach it.

Anyway, closing it now.  Thank you!

Ludo’.

  reply	other threads:[~2019-07-04 15:13 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
2019-07-04  8:04                 ` Robert Vollmert
2019-07-04 15:12                   ` Ludovic Courtès [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87bly93kbj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36443-done@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).