unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 18747@debbugs.gnu.org
Subject: bug#18747: Fixed-output derivations are not substituted
Date: Thu, 16 Oct 2014 17:43:23 +0200	[thread overview]
Message-ID: <874mv458bo.fsf@gnu.org> (raw)
In-Reply-To: <87h9z4594k.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 16 Oct 2014 17:26:03 +0200")

I just realized that this is fixed by just removing #:local-build? #t
from (guix download).

Initially #:local-build? (aka. ‘preferLocalBuild’) meant “avoid
offloading this derivation”, but Nix commit 55586527 (June 2013) changed
it to “avoid offloading *or substituting* this derivation”, which I
somehow overlooked for all this time.

I think we to distinguish between whether to offload and whether to
substitute.  Typically, we don’t want to offload downloads, because
that’s inefficient.  However, we may want to substitute downloads,
because then if the upstream download URL has become invalid, we can
still get the substitute from hydra.gnu.org.

Until then, I think I’ll just comment out #:local-build? #t in (guix
download) and friends.

Thoughts?

Thanks,
Ludo’.

  reply	other threads:[~2014-10-16 15:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 15:26 bug#18747: Fixed-output derivations are not substituted Ludovic Courtès
2014-10-16 15:43 ` Ludovic Courtès [this message]
2014-10-16 15:46   ` Ludovic Courtès
2015-07-01 15:21     ` bug#18747: [PATCH] Distinguish between “offloadability” and “substitutability” Ludovic Courtès
     [not found]     ` <87d20boqcw.fsf_-_@gnu.org>
2015-07-01 15:27       ` Eelco Dolstra
     [not found]       ` <559406C6.7040209@logicblox.com>
2015-07-01 21:14         ` Ludovic Courtès
2015-07-02 22:33     ` bug#18747: Fixed-output derivations are not substituted Ludovic Courtès

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=874mv458bo.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=18747@debbugs.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/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).