all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: Publishing an Official Statement on Self-Hosted Compilers
Date: Thu, 12 May 2016 12:05:36 +0200	[thread overview]
Message-ID: <871t544cn8.fsf@gnu.org> (raw)
In-Reply-To: <1462839088.1794949.602935177.45787E29@webmail.messagingengine.com> (Alex Griffin's message of "Mon, 09 May 2016 19:11:28 -0500")

Hi!

Alex Griffin <a@ajgrf.com> skribis:

> I've put my initial notes in a git repository
> [here](https://gitlab.com/ajgrf/bootstrapping-compilers/blob/master/notes.org).
> They are in a very rough state, but mostly everything is there in some
> form. If anyone has any thoughts please let me know! 

I like it.  :-)

I think the bit about the “trusting trust” attack should go under “The
Problem”.  Specifically, I would suggest expounding on the software
freedom bit (the fact that users must be provided with the Corresponding
Source), and the reproducibility bit (allow people to build from source
and to ensure the binaries correspond to the source), and then on
security (“trusting trust”.)

WDYT?

We should then discuss it with the repro-builds folks, and probably
contact a bunch of compiler writers to get initial feedback.

Thanks,
Ludo’.

PS: I would suggest wrapping lines in notes.org, which would make it
    easier to read IMO, and also facilitate patch handling.

  reply	other threads:[~2016-05-14 20:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 14:52 Publishing an Official Statement on Self-Hosted Compilers Alex Griffin
2016-05-05 22:30 ` Efraim Flashner
2016-05-06  8:07   ` Pjotr Prins
2016-05-06  9:08 ` John Darrington
2016-05-06 10:09 ` Ludovic Courtès
2016-05-06 17:13   ` Alex Griffin
2016-05-09  8:29     ` Ludovic Courtès
2016-05-10  0:11       ` Alex Griffin
2016-05-12 10:05         ` Ludovic Courtès [this message]
2016-05-12 10:05         ` Ludovic Courtès
2016-05-21 23:22           ` Alex Griffin

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=871t544cn8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=a@ajgrf.com \
    --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 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.