unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Glenn Morris <rgm@gnu.org>, info@protesilaos.com, 48661@debbugs.gnu.org
Subject: bug#48661: reproducibility: build date in modus-themes.info
Date: Wed, 26 May 2021 12:40:11 +0200	[thread overview]
Message-ID: <878s41g4ms.fsf@igel.home> (raw)
In-Reply-To: <877djldcbl.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Wed, 26 May 2021 12:22:22 +0200")

On Mai 26 2021, Kévin Le Gouguec wrote:

> Question from the peanut gallery: are timestamp information really
> verboten in reproducible builds?  I was led to believe that the
> SOURCE_DATE_EPOCH mechanism was introduced to allow programs to keep
> embedding this information, while giving packagers the means to assert
> reproducibility.

That requires support for SOURCE_DATE_EPOCH in each place a timestamp is
generated.  For example, gcc does that for __DATE__ and __TIME__.  If
org wants to keep the timestamp it should add support for
SOURCE_DATE_EPOCH.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."





      reply	other threads:[~2021-05-26 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 21:50 bug#48661: reproducibility: build date in modus-themes.info Glenn Morris
2021-05-26  9:15 ` Protesilaos Stavrou
2021-05-26 10:22 ` Kévin Le Gouguec
2021-05-26 10:40   ` Andreas Schwab [this message]

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s41g4ms.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=48661@debbugs.gnu.org \
    --cc=info@protesilaos.com \
    --cc=kevin.legouguec@gmail.com \
    --cc=rgm@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).