all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Status update on reproducible builds in Guix
Date: Sun, 05 Nov 2017 16:49:01 +0100	[thread overview]
Message-ID: <87efpcsp3m.fsf@gnu.org> (raw)
In-Reply-To: <87y3nqwmb7.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Wed, 01 Nov 2017 07:22:04 +0100")

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> Ludovic Courtès writes:
>
>> Here’s an update on reproducibility in Guix:
>>
>>   https://www.gnu.org/software/guix/news/reproducible-builds-a-status-update.html
>
> At least 78% to possibly 91% reproduciblility of packages is not bad.
>
> Is there a (small) core that is already 100% reprocucible, like the
> installation binaries/USB installer, bare-bones.tmpl or even
> lightweight-desktop.tmpl?

Good question!  I think as soon as you have Python .pyc files in the
dependency graph (reference graph), there are non-reproducible bits.  We
certainly have Python stuff in the base system reference graph, so
that’s one thing we should fix most urgently I guess.

Ludo’.

  reply	other threads:[~2017-11-05 15:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 10:33 Status update on reproducible builds in Guix Ludovic Courtès
2017-11-01  6:22 ` Jan Nieuwenhuizen
2017-11-05 15:49   ` Ludovic Courtès [this message]
2017-11-05 19:04     ` Gábor Boskovits
2017-11-05 19:16       ` Hartmut Goebel
2017-11-05 19:17       ` ng0
2017-11-06  8:52       ` Ludovic Courtès
2017-11-06 10:19         ` Hartmut Goebel
2017-11-06 11:47           ` Gábor Boskovits
2017-11-07  9:55             ` Eric Myhre
2017-11-07 10:12               ` Hartmut Goebel
2017-11-06 21:29           ` Marius Bakke
2017-11-07  9:16             ` Hartmut Goebel
2017-11-07 19:00               ` Marius Bakke
2017-11-06 21:14         ` Marius Bakke

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=87efpcsp3m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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.