From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: reproducible builds and debugging information
Date: Mon, 30 Mar 2015 21:42:57 +0200 [thread overview]
Message-ID: <87d23q5l1a.fsf@gnu.org> (raw)
In-Reply-To: <87d23rbttt.fsf@netris.org> (Mark H. Weaver's message of "Sun, 29 Mar 2015 13:24:14 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> I think what Tomáš suggested above does not conflict with the design of
> Nix and Guix. As I understand it, he's suggesting that we have
> 'outputs' default to '("out" "debug") but then the debug outputs would
> be immediately discarded for most packages. This would save both disk
> space and slave->hydra bandwidth. Users could then get the debug
> outputs by building the package locally.
OK, I see. The thing is that “immediately discarded” really means
“after the build completed and they’ve been put in store.” So the build
machine would still need to be able to cope with the additional storage
requirements.
Also, currently I don’t see how we could avoid transferring the “debug”
output back to the master: when the daemon offloads a derivation build,
it really expects to be able to get all the outputs back. We could hack
the daemon to special-case “debug” outputs but that doesn’t seem great.
Dunno, maybe I’m still too blinded by what’s possible now to think about
what could be made possible. :-)
Thanks,
Ludo’.
prev parent reply other threads:[~2015-03-30 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 17:26 reproducible builds and debugging information Tomáš Čech
2015-03-24 21:09 ` Ludovic Courtès
2015-03-25 0:33 ` Tomáš Čech
2015-03-26 21:21 ` Ludovic Courtès
2015-03-26 21:51 ` Tomáš Čech
2015-03-27 21:24 ` Ludovic Courtès
2015-03-27 21:55 ` Tomáš Čech
2015-03-28 17:41 ` Ludovic Courtès
2015-03-29 17:24 ` Mark H Weaver
2015-03-30 19:42 ` 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=87d23q5l1a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.