From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 'guix build' and garbage collection
Date: Fri, 07 Apr 2017 21:53:07 +0200 [thread overview]
Message-ID: <87pogouh98.fsf@gnu.org> (raw)
In-Reply-To: <87inmgg9qd.fsf@gmail.com> (Chris Marusich's message of "Thu, 06 Apr 2017 20:47:06 -0700")
Chris Marusich <cmmarusich@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hi!
>>
>> Chris Marusich <cmmarusich@gmail.com> skribis:
>>
>>> Do you know why the intensional model hasn't been deployed in the 11
>>> years since the thesis was published? To learn more, I can think of a
>>> few places to look (Nix email lists, other Nix-related research papers),
>>> but if you have specific recommendations, it would be helpful!
>>
>> The intensional model (content-address item) works well if and only if
>> packages are 100% bit-reproducible, which they are not (yet!).
>>
>> Also I’m not sure how substitutes could work with this model since one
>> cannot refer to the build result until it’s available.
>
> FYI, section 6.4.4 (p. 157) of Eelco's thesis describes how substitution
> works in the intensional model. When performing substitution for a
> store path p, if a trusted substitute for p has been registered, then it
> is tried, and the substitution is considered successful if and only if
> the output's content-addressed store path equals p.
Oh indeed, thanks for the reminder!
Ludo’.
prev parent reply other threads:[~2017-04-07 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 1:06 'guix build' and garbage collection Chris Marusich
2017-04-02 9:30 ` Ludovic Courtès
2017-04-03 6:40 ` Chris Marusich
2017-04-03 8:53 ` Ludovic Courtès
2017-04-03 16:29 ` Chris Marusich
2017-04-04 12:13 ` Ludovic Courtès
2017-04-07 3:47 ` Chris Marusich
2017-04-07 19:53 ` Ludovic Courtès [this message]
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=87pogouh98.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@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 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.