From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Reproducible builds: a means to an end
Date: Mon, 16 Nov 2015 15:44:40 +0100 [thread overview]
Message-ID: <idjvb92atrb.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87bnb0egb1.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> I published a note on how I think reproducible builds fit in the bigger
> picture of user freedom and user autonomy, and what role Guix can play:
>
> https://savannah.gnu.org/forum/forum.php?forum_id=8407
That was a very nice read!
I wonder how we as a project could help the reproducible builds project
and/or directly benefit from their findings. Are there ready-made
patches we could apply to our package recipes? Or should we just wait
for upstream projects to be fixed?
The utility of “guix challenge” is much reduced when for so many
packages we do not actually have reproducible builds.
(Maybe we could have a page that lists packages that “guix challenge”
suggests as having non-reproducible builds.)
Can we automate some fixes, such as disabling timestamps? (I see, for
example, that the Python REPL tells me when it was built.)
~~ Ricardo
next prev parent reply other threads:[~2015-11-16 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 14:55 Reproducible builds: a means to an end Ludovic Courtès
2015-11-12 20:13 ` Jan Synáček
2015-11-16 14:44 ` Ricardo Wurmus [this message]
2015-11-16 15:40 ` Ludovic Courtès
2015-11-17 18:01 ` Alex Vong
2015-11-17 21:45 ` Ludovic Courtès
2015-11-18 13:57 ` Alex Vong
2015-11-18 18:20 ` Ludovic Courtès
2015-11-19 8:14 ` Efraim Flashner
2015-11-19 14:45 ` Alex Vong
2015-11-19 16:09 ` Ludovic Courtès
2015-11-20 6:22 ` Alex Vong
2015-11-21 10:41 ` Ludovic Courtès
2015-11-21 13:53 ` Alex Vong
2015-11-21 15:50 ` 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=idjvb92atrb.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--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.