From: Leo Famulari <leo@famulari.name>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: [v3] Erlang
Date: Mon, 4 Apr 2016 12:50:12 -0400 [thread overview]
Message-ID: <20160404165012.GA11014@jasmine> (raw)
In-Reply-To: <20160404082802.GA29212@thebird.nl>
On Mon, Apr 04, 2016 at 10:28:02AM +0200, Pjotr Prins wrote:
> On Sun, Apr 03, 2016 at 11:39:24PM -0400, Leo Famulari wrote:
> > Debian's package exhibits this problem. The timestamps are generated in
> > the following places in the source code. I don't know how to approach
> > this problem.
> >
> > lib/kernel/test/global_SUITE_data/global_trace.erl: io:format("The trace was generated at ~p~n", [EndTime]),
> > lib/reltool/bin/reltool.escript: lists:flatten(io_lib:format("%% ~s generated at ~w ~w\n~p.\n\n",
> > lib/reltool/src/reltool_server.erl: IoList = io_lib:format("%% config generated at ~w ~w\n~p.\n\n",
> > lib/reltool/src/reltool_target.erl: RelIoList = io_lib:format("%% rel generated at ~w ~w\n~p.\n\n",
> > lib/reltool/src/reltool_target.erl: ScriptIoList = io_lib:format("%% script generated at ~w ~w\n~p.\n\n",
> > lib/reltool/src/reltool_target.erl: AppIoList = io_lib:format("%% app generated at ~w ~w\n~p.\n\n",
> > lib/reltool/src/reltool_target.erl: AppIoList = io_lib:format("%% app generated at ~w ~w\n~p.\n\n",
> > lib/runtime_tools/src/erts_alloc_config.erl: "generated at ~w-~2..0w-~2..0w ~2..0w:~2..0w.~2..0w by "
> > lib/sasl/src/systools_make.erl: io:format(Fd, "%% script generated at ~w ~w\n~p.\n",
> > lib/wx/src/gen/gl.erl:%% The program object's information log is updated and the program is generated at the time
>
> If there is no easy work around I suggest simply patching them. Fortunately
> the Erlang compiler does not change much at this level.
The ideal solution would be to use the value of the environment variable
SOURCE_DATE_EPOCH if it is set, and else to behave as it does now.
> We can also contact Joe Armstrong, the author of Erlang, to discuss
> this point. He appears to be approachable. I am sure he is open to
> the idea of deterministic builds in a deterministic build system ;)
I could go to the Erlang IRC channel or forums (whatever they use) and
ask for advice. Since you are actually using Erlang, I think you would
be the better person to contact Joe Armstrong himself, if we decide to
do that.
next prev parent reply other threads:[~2016-04-04 16:50 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
2016-04-04 3:39 ` [v3] Erlang Leo Famulari
2016-04-04 8:28 ` Pjotr Prins
2016-04-04 16:50 ` Leo Famulari [this message]
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=20160404165012.GA11014@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).