all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Eli Zaretskii" <eliz@gnu.org>
Cc: alezost@gmail.com, emacs-devel@gnu.org
Subject: Re: [PATCH PING] Honor 'SOURCE_DATE_EPOCH' when generating autoloads.
Date: Mon, 07 Dec 2015 18:36:19 +0000	[thread overview]
Message-ID: <CAArVCkQK36RwUyk+X9Srj8pFmMe_t3cqP5XDwpU=ChBj3SR5eA@mail.gmail.com> (raw)
In-Reply-To: <87two3475d.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

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?

[-- Attachment #2: Type: text/html, Size: 2137 bytes --]

  reply	other threads:[~2015-12-07 18:36 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 17:03 [PATCH] Honor 'SOURCE_DATE_EPOCH' when generating autoloads Ludovic Courtès
2015-11-29 10:44 ` [PATCH PING] " Ludovic Courtès
2015-11-29 16:02   ` Eli Zaretskii
2015-11-29 16:57     ` Ludovic Courtès
2015-11-29 18:12       ` Eli Zaretskii
2015-11-29 20:38         ` Ludovic Courtès
2015-11-30 17:00         ` John Wiegley
2015-11-30 19:30           ` Ludovic Courtès
2015-12-07 18:36             ` Philipp Stephani [this message]
2015-12-07 18:58               ` Paul Eggert
2015-12-07 19:00                 ` Philipp Stephani
2015-12-07 19:14                   ` Paul Eggert
2015-12-20 12:48                     ` Philipp Stephani
2015-12-20 16:37                       ` Eli Zaretskii
2015-12-20 18:39                         ` Philipp Stephani
2015-12-20 19:03                           ` Eli Zaretskii
2015-12-20 21:27                           ` Paul Eggert
2015-12-23  1:13                             ` John Wiegley
2015-12-23 16:01                               ` Philipp Stephani
2015-12-23 16:39                                 ` Eli Zaretskii
2015-12-23 16:52                                   ` Philipp Stephani
2015-12-23 17:10                                     ` Eli Zaretskii
2015-12-23 17:38                                       ` Philipp Stephani
2015-12-23 21:09                                         ` Paul Eggert
2015-12-24  3:33                                           ` Eli Zaretskii
2015-12-24  6:54                                             ` Paul Eggert
2015-12-24 16:18                                               ` Eli Zaretskii
2015-12-27  9:53                                     ` Philipp Stephani
2015-12-27 16:10                                       ` Eli Zaretskii
2016-02-29 21:52                                         ` Philipp Stephani
2016-03-01 16:36                                           ` Paul Eggert
2016-03-01 21:46                                             ` Philipp Stephani
2016-03-02 18:24                                               ` Paul Eggert
2016-03-02 18:30                                                 ` Philipp Stephani
2016-03-22 13:30                                                   ` Philipp Stephani
2016-03-22 20:37                                                     ` Paul Eggert
2016-03-22 21:46                                                       ` Philipp Stephani
2016-03-22 21:58                                                         ` Paul Eggert
2016-03-23  8:03                                                         ` Andreas Schwab
2016-04-06 21:29                                                           ` Philipp Stephani
2015-12-27 23:26                                       ` Paul Eggert
2015-12-28 16:26                                         ` Eli Zaretskii
2015-12-28 18:00                                           ` Paul Eggert
2015-12-28 18:23                                             ` Eli Zaretskii
2015-12-29  3:01                                               ` Paul Eggert
2015-12-29 15:38                                                 ` Eli Zaretskii
2015-12-29 16:47                                                   ` Paul Eggert
2015-12-29 17:59                                                     ` Eli Zaretskii
2015-12-29 20:33                                                       ` Paul Eggert
2015-12-07 23:11               ` Ludovic Courtès
2015-11-30  9:22       ` Alex Kost
2015-11-29 20:22   ` Paul Eggert
2015-11-29 20:42     ` Ludovic Courtès

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='CAArVCkQK36RwUyk+X9Srj8pFmMe_t3cqP5XDwpU=ChBj3SR5eA@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=alezost@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.