From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [v2 0/1] Erlang
Date: Sun, 03 Apr 2016 23:26:48 +0200 [thread overview]
Message-ID: <8737r2bcyv.fsf@gnu.org> (raw)
In-Reply-To: <20160402022054.GA17152@jasmine> (Leo Famulari's message of "Fri, 1 Apr 2016 22:20:54 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Fri, Apr 01, 2016 at 10:19:11AM +0200, Pjotr Prins wrote:
>>
>> On Thu, Mar 31, 2016 at 03:35:44PM -0400, Leo Famulari wrote:
>> > This adds Erlang.
>> >
>> > Originally written by Steve Sprang, I added the man pages and fixed all
>> > the "FHS bugs" I noticed.
>> >
>> > Pjotr used it to build a working Elixir:
>> > http://lists.gnu.org/archive/html/guix-devel/2016-03/msg00999.html
>>
>> Better even, I am actually using that Elixir and Erlang :). Please
>> push when there are no other issues.
>
> Cool! From my point of view, there are no blocking issues.
>
> There are two sources of non-determinism when building repeatedly on the
> same machine.
>
> All the .beam files have timestamps and build paths embedded [0]. This
> is a known issue without a clear solution. The build paths don't seem so
> bad to me, since my understanding is that they are set deterministically
> by the Guix builder.
>
> There are also some .script files that also embed timestamps in a human
> readable string. Grepping for the string makes it easy to find the
> source of this. We could patch the timestamp format string with the
> value of SOURCE_DATE_EPOCH.
>
> Thoughts?
>
> [0]
> https://wiki.debian.org/ReproducibleBuilds/TimestampsInBeamFiles
A patch along the lines of the one of the page above should do the work
for beam files, no? We’d have to change DEB_BUILD_DATE to
SOURCE_DATE_EPOCH, and remove regexp-matching from there.
Ludo’ (who’s never written Erlang code ;-)).
next prev parent reply other threads:[~2016-04-03 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 19:35 [v2 0/1] Erlang Leo Famulari
2016-03-31 19:35 ` [v2 1/1] gnu: Add erlang Leo Famulari
2016-04-01 8:19 ` [v2 0/1] Erlang Pjotr Prins
2016-04-02 2:20 ` Leo Famulari
2016-04-03 21:26 ` Ludovic Courtès [this message]
2016-04-04 3:39 ` [v3] Erlang Leo Famulari
2016-04-04 8:28 ` Pjotr Prins
2016-04-04 16:50 ` Leo Famulari
2016-04-04 17:49 ` Leo Famulari
2016-04-04 18:15 ` Pjotr Prins
2016-04-05 10:02 ` Pjotr Prins
2016-04-05 18:46 ` Leo Famulari
2016-04-09 10:56 ` Pjotr Prins
2016-05-23 11:48 ` Pjotr Prins
2016-05-23 18:59 ` Leo Famulari
2016-04-04 18:32 ` Pjotr Prins
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737r2bcyv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).