From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: reproducible builds and debugging information
Date: Sun, 29 Mar 2015 13:24:14 -0400 [thread overview]
Message-ID: <87d23rbttt.fsf@netris.org> (raw)
In-Reply-To: <87ego93tq6.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 28 Mar 2015 18:41:21 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Tomáš Čech <sleep_walker@gnu.org> skribis:
>
>> On Fri, Mar 27, 2015 at 10:24:22PM +0100, Ludovic Courtès wrote:
>>>Tomáš Čech <sleep_walker@gnu.org> skribis:
>>>
>>>> Imagine situation where you added "debug" output to every package and
>>>> after each build the newly generated store with debug information is
>>>> deleted (carefully, not to corrupt database, of course). Your hash
>>>> still will be the same.
>>>
>>>I see what you mean, but again, that’s not how it works, and I would
>>>argue that it’s not desirable.
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.
I'm not necessarily advocating that we should do this, but wanted to
help facilitate communication.
Mark
next prev parent reply other threads:[~2015-03-29 17:23 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 [this message]
2015-03-30 19:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d23rbttt.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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.