all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: ludo@gnu.org
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: How to reduce our vulnerability from self-hosted compilers
Date: Fri, 27 Feb 2015 12:25:53 +0100	[thread overview]
Message-ID: <CAKrPhPPHbnoefeJ6_+hU2dEkUqB56WgfPTRLDJJ1CRF5Gd7CCQ@mail.gmail.com> (raw)

ludo@gnu.org (Ludovic Courtès) writes:

> It think it’s a good idea, but I wonder if it is generally applicable.
>
> For instance, ISTR that GHC can be built with a couple of older versions
> whereas MIT Scheme may well require itself.  What exactly is possible is
> not always well-documented and sometimes only known to few people.

For GHC (at least currently) it is well documented, see
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Tools

In principle I agree with Mark's suggestion. However, I have a couple of
comments.

My intention was to build GHC and get rid of the required GHC bootstrap
binary from GUIX altogether. With the current patch the store doesn't
need to include the bootstrap binaries which, when uncompressed,
requires 940MB! The compressed bootstrap binary archive is "only" 68MB.
(I'm thinking about download time here. But maybe we could force a local
"build" as discussed for TeXLive.)

The other point is: given that we know the hash of the tar file, if
somebody manages to hack them, we will detect it.

Regards,
Fede

             reply	other threads:[~2015-02-27 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 11:25 Federico Beffa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-26 23:22 How to reduce our vulnerability from self-hosted compilers Mark H Weaver
2015-02-27 10:49 ` Ludovic Courtès
2015-02-27 21:12   ` Andreas Enge

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=CAKrPhPPHbnoefeJ6_+hU2dEkUqB56WgfPTRLDJJ1CRF5Gd7CCQ@mail.gmail.com \
    --to=beffa@ieee.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.