From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Removing compilers that cannot be bootstrapped
Date: Sat, 26 Mar 2016 00:08:09 +0100 [thread overview]
Message-ID: <87d1qi40me.fsf@gnu.org> (raw)
In-Reply-To: <20160324031126.GA22569@jasmine> (Leo Famulari's message of "Wed, 23 Mar 2016 23:11:26 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Mar 23, 2016 at 03:49:33PM -0700, Christopher Allan Webber wrote:
>> Ludovic Courtès writes:
>>
>> > Christopher Allan Webber <cwebber@dustycloud.org> skribis:
>> >
>> >> Let me give an even shorter-term solution: maybe there is a way to mark
>> >> things as risky from a trust perspective when it comes to bootstrapping?
>> >> Maybe we could do something like:
>> >>
>> >> (define-public ghc
>> >> (package
>> >> (name "ghc")
>> >> (version "7.10.2")
>> >> ;; [... bla bla ...]
>> >> (properties '(("bootstrap-untrusted" #t)))))
>> >
>> > Why not, but what would be the correspond warning, and the expected
>> > effect?
>>
>> A warning, or maybe even also a:
>>
>> guix package -i foo --only-reproducible
>>
>> which could error?
Hmm or --only-traceable?
> If we decide to do something like that, we should decide if we want the
> word 'reproducible' to mean bit-for-bit reproducibility.
The problem is that big binary blobs like GHC’s are necessarily
bit-for-bit reproducible. :-)
Ludo’.
next prev parent reply other threads:[~2016-03-25 23:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 17:54 Removing compilers that cannot be bootstrapped Thompson, David
2016-03-21 19:15 ` Taylan Ulrich Bayırlı/Kammer
2016-03-21 19:22 ` Taylan Ulrich Bayırlı/Kammer
2016-03-21 19:32 ` Andreas Enge
2016-03-21 22:43 ` rain1
2016-03-22 16:23 ` Ludovic Courtès
2016-03-21 22:48 ` Ludovic Courtès
2016-03-22 9:56 ` Jookia
2016-03-22 16:25 ` Ludovic Courtès
2016-03-22 14:57 ` Eric Bavier
2016-03-22 16:22 ` Ludovic Courtès
2016-03-22 22:29 ` Christopher Allan Webber
2016-03-23 22:12 ` Ludovic Courtès
2016-03-23 22:49 ` Christopher Allan Webber
2016-03-24 3:11 ` Leo Famulari
2016-03-25 23:08 ` Ludovic Courtès [this message]
2016-03-26 0:22 ` Leo Famulari
2016-03-26 6:40 ` Chris Marusich
2016-03-26 6:55 ` Chris Marusich
2016-03-26 9:02 ` Jookia
2016-03-26 14:05 ` Alex Vong
2016-03-26 8:12 ` Ricardo Wurmus
2016-03-26 9:23 ` Jookia
2016-03-26 14:31 ` Ludovic Courtès
2016-03-26 17:19 ` Christopher Allan Webber
2016-03-26 6:51 ` John Darrington
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=87d1qi40me.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.