From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Removing compilers that cannot be bootstrapped
Date: Wed, 23 Mar 2016 23:12:27 +0100 [thread overview]
Message-ID: <87bn64u9mc.fsf@gnu.org> (raw)
In-Reply-To: <87h9fyw3j8.fsf@dustycloud.org> (Christopher Allan Webber's message of "Tue, 22 Mar 2016 15:29:08 -0700")
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?
On one hand, a warning might annoy people since there’s nothing they can
do; on the other hand, it can help raise awareness.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2016-03-23 22:12 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 [this message]
2016-03-23 22:49 ` Christopher Allan Webber
2016-03-24 3:11 ` Leo Famulari
2016-03-25 23:08 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn64u9mc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).