From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_REPRODUCIBLE issues
Date: Sat, 4 Nov 2017 23:24:41 +0100 [thread overview]
Message-ID: <20171104232441.4d7a4754@windsurf> (raw)
In-Reply-To: <5c52008b-1ffa-7260-8681-5abeecd09665@mind.be>
Hello,
On Sat, 4 Nov 2017 20:53:27 +0100, Arnout Vandecappelle wrote:
> > So I don't really agree that it useless. What we could perhaps do is to
> > only export our value for SOURCE_DATE_EPOCH if not already set in the
> > enviroment, so you can set it outside Buildroot if you want a different
> > behaviour.
>
> Well, the proposed solution of using a config variable sounds OK. Only, I think
> it would make more sense to have a config variable with a date, rather than a
> commit ID.
Why would we want a config option, rather than just comply with the
SOURCE_DATE_EPOCH environment variable, if already defined in the
environment?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-04 22:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 14:40 [Buildroot] BR2_REPRODUCIBLE issues Einar Jón Gunnarsson
2017-11-03 20:15 ` Peter Korsgaard
2017-11-04 19:53 ` Arnout Vandecappelle
2017-11-04 20:49 ` Peter Korsgaard
2017-11-04 22:24 ` Thomas Petazzoni [this message]
2017-11-05 8:46 ` Yann E. MORIN
2017-11-06 9:43 ` Einar Jón
2017-11-06 17:50 ` Yann E. MORIN
2017-11-06 20:39 ` Peter Korsgaard
2017-11-06 22:50 ` Arnout Vandecappelle
2017-11-08 18:00 ` Yann E. MORIN
2017-11-08 18:59 ` Peter Korsgaard
2017-11-08 22:07 ` Arnout Vandecappelle
2017-11-06 21:34 ` Arnout Vandecappelle
2017-11-06 21:37 ` Yann E. MORIN
2017-11-05 8:35 ` Yann E. MORIN
2017-11-05 8:54 ` Peter Korsgaard
2017-11-05 8:59 ` Yann E. MORIN
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=20171104232441.4d7a4754@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox