From: ludo@gnu.org (Ludovic Courtès)
To: Eelco Dolstra <eelco.dolstra@logicblox.com>
Cc: 18747@debbugs.gnu.org, nix-dev@lists.science.uu.nl
Subject: bug#18747: [PATCH] Distinguish between “offloadability” and “substitutability”
Date: Wed, 01 Jul 2015 23:14:43 +0200 [thread overview]
Message-ID: <877fqjmvgc.fsf__32350.0930135653$1435785327$gmane$org@gnu.org> (raw)
In-Reply-To: <559406C6.7040209@logicblox.com> (Eelco Dolstra's message of "Wed, 01 Jul 2015 17:27:02 +0200")
Eelco Dolstra <eelco.dolstra@logicblox.com> skribis:
> On 01/07/15 17:21, Ludovic Courtès wrote:
>
>> Nix commit 55586527 (June 2013) changed the semantics of
>> ‘preferLocalBuild’ from “avoid offloading this derivation” to “avoid
>> offloading *or substituting* this derivation” (see
>> <http://bugs.gnu.org/18747>.)
>>
>> This patch introduces a new special key, ‘substitution’, to specify
>> whether a derivation should be substituted. ‘preferLocalBuild’ is kept,
>> but its initial semantics is restored.
>
> Have you seen
> https://github.com/NixOS/nix/commit/b64988bb3585478676585a0f0aecbcf4e11d4432,
> which essentially does the same thing?
I hadn’t, but that’s perfect–we’re on the same page. ;-)
Thanks!
Ludo’.
next prev parent reply other threads:[~2015-07-01 21:15 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
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 [this message]
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='877fqjmvgc.fsf__32350.0930135653$1435785327$gmane$org@gnu.org' \
--to=ludo@gnu.org \
--cc=18747@debbugs.gnu.org \
--cc=eelco.dolstra@logicblox.com \
--cc=nix-dev@lists.science.uu.nl \
/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).