Ludovic Courtès <ludo@gnu.org> schrieb am Mo., 30. Nov. 2015 um 20:30 Uhr:

> John Wiegley <jwiegley@gmail.com> skribis:
>
> >>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> >
> >>> This is obviously the first patch of a series. It does not make Emacs
> >>> itself bit-reproducible, but it makes Emacs packages bit-reproducible.
> >
> >> I'd prefer to have the whole series, to see where this is going, and
> then
> >> commit them in one go. But that's me. John?
> >
> > Yes, I too would like to see this evolve on a feature branch until the
> whole
> > series is ready, after which Eli and I can review before moving into
> master.
> >
> > How does that sound, Alex, Ludovic?
>
> From the Guix viewpoint, we need an immediate fix for this issue.  So
> we’ll be using the patch I posted until Emacs has an appropriate
> solution, which may be along the lines of what Paul suggested.
>
> We’ll surely look at making Emacs itself reproducible (and perhaps the
> Debian folks already have patches floating around), but no ETA.
>

I'm interested in reproducible builds as well; do you already have some
design ideas how to tackle this problem? So far I've found three areas
where Emacs itself builds something that could be reproducible (dumping,
generating autoload files, byte compilation), and a couple of data items
that cause irreproducibility (host names, timestamps, absolute paths). As a
rough sketch, Emacs could be made to detect an environment variable such as
EMACS_DETERMINISTIC_BUILD, causing various code paths in the core and in
the Elisp files to become deterministic. Would that be feasible?