From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Re: [PATCH PING] Honor 'SOURCE_DATE_EPOCH' when generating autoloads. Date: Mon, 07 Dec 2015 18:36:19 +0000 Message-ID: References: <87k2ph3mgx.fsf@gnu.org> <87io4lnkyz.fsf@gnu.org> <83mvtwoktg.fsf@gnu.org> <878u5gkakj.fsf@gnu.org> <83a8pwoesc.fsf@gnu.org> <87two3475d.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0102def4a860d605265322d4 X-Trace: ger.gmane.org 1449513405 10619 80.91.229.3 (7 Dec 2015 18:36:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Dec 2015 18:36:45 +0000 (UTC) Cc: alezost@gmail.com, emacs-devel@gnu.org To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 07 19:36:41 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a60eM-0004r0-FX for ged-emacs-devel@m.gmane.org; Mon, 07 Dec 2015 19:36:38 +0100 Original-Received: from localhost ([::1]:55983 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a60eL-00038f-Pt for ged-emacs-devel@m.gmane.org; Mon, 07 Dec 2015 13:36:37 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34910) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a60eI-00038V-De for emacs-devel@gnu.org; Mon, 07 Dec 2015 13:36:35 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a60eH-0007f7-Eb for emacs-devel@gnu.org; Mon, 07 Dec 2015 13:36:34 -0500 Original-Received: from mail-wm0-x22f.google.com ([2a00:1450:400c:c09::22f]:33903) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a60eD-0007ds-Td; Mon, 07 Dec 2015 13:36:30 -0500 Original-Received: by wmvv187 with SMTP id v187so180274220wmv.1; Mon, 07 Dec 2015 10:36:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=XY+iTLct28iUltVp/6uabOzZ0K5GKnmjhH0Tj40IpRE=; b=SofMXPl2pHVNLzbb5q98qKZej7hNnjL5YYHCfrozOuoJktqkKeGuTivbOjw4Ou5u74 YK6+VbhJeO36R7SOIkN6Dr0ANWElTy6lpCqVSC8eW84TDu+KDWXyD2G8ooLNk59N4t5F 8o3LeX/eG3DLm5wgH6wSG2Z+2iBPoVsaSG5FiABeHZ7O+lGX7rpaIVpsRCmushF+5mHU AOkoxodiYX8bARnMkMPt5snu5xYlmxQFoJUp4TElyZlKhQK0nWuWfQ+u1DkXgmhQdJr0 UZNnpGYk6Gr4PV548hq/SBKsLAvLIoXq4JiStZzQBjB3MHcztIk8MDXsHBZYB3/goBjb q82g== X-Received: by 10.194.87.39 with SMTP id u7mr34975776wjz.11.1449513389152; Mon, 07 Dec 2015 10:36:29 -0800 (PST) In-Reply-To: <87two3475d.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::22f X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:195960 Archived-At: --089e0102def4a860d605265322d4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s schrieb am Mo., 30. Nov. 2015 um 20:30 = Uhr: > John Wiegley skribis: > > >>>>>> Eli Zaretskii 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=E2=80=99ll be using the patch I posted until Emacs has an appropriate > solution, which may be along the lines of what Paul suggested. > > We=E2=80=99ll surely look at making Emacs itself reproducible (and perhap= s 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? --089e0102def4a860d605265322d4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Ludovi= c Court=C3=A8s <ludo@gnu.org> sch= rieb am Mo., 30. Nov. 2015 um 20:30=C2=A0Uhr:
John Wiegley <jwiegley@gmail.com> skribis:

>>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> This is obviously the first patch of a series. It does not mak= e Emacs
>>> itself bit-reproducible, but it makes Emacs packages bit-repro= ducible.
>
>> I'd prefer to have the whole series, to see where this is goin= g, 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 m= aster.
>
> How does that sound, Alex, Ludovic?

>From the Guix viewpoint, we need an immediate fix for this issue.=C2=A0 So<= br> we=E2=80=99ll be using the patch I posted until Emacs has an appropriate solution, which may be along the lines of what Paul suggested.

We=E2=80=99ll 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, tim= estamps, 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. Woul= d that be feasible?=C2=A0
--089e0102def4a860d605265322d4--