All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: "Bystricky, Juro" <juro.bystricky@intel.com>,
	Martin Jansa <martin.jansa@gmail.com>
Cc: "jurobystricky@hotmail.com" <jurobystricky@hotmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] Reproducible binaries
Date: Thu, 27 Apr 2017 10:50:10 +0100	[thread overview]
Message-ID: <1493286610.26953.1.camel@linux.intel.com> (raw)
In-Reply-To: <6E51916E4A1F32428260031F4C7CD2B61194DECB@ORSMSX112.amr.corp.intel.com>

On Wed, 2017-04-26 at 19:50 +0000, Bystricky, Juro wrote:
> > I wasnted to say "passing the seed value" through some separate
> > variable
> > which is easy to override from somewhere else.
> > 
> > e.g.
> > export PRELINK_TIMESTAMP=`git log -1 --pretty=%ct `
> > 
> > in image-prelink.bbclass:prelink_image() is a bit difficult to
> > override.
> > 
> 
> I think it is best to keep all reproducible build related variables
> gathered together, 
> so bitbake.conf seems like a natural place (same place as the
> variable BUILD_REPRODUCIBLE_BINARIES),
> i.e something like:
> 
> PRELINK_TIMESTAMP ??=`git log -1 --pretty=%ct `
> 
> A single "general purpose" fallback timestamp variable (not specific
> to prelinking) would be my
> preference. Unfortunately, the timestamps may need to come in various
> different formats...

One option for a single general purpose timestamp variable is just to
use a static value. Guix[1] just set the value of SOURCE_DATE_EPOCH to
1[2].

Joshua

1. https://www.gnu.org/software/guix/
2. http://git.savannah.gnu.org/cgit/guix.git/tree/guix/build/gnu-build-
system.scm#n42


  reply	other threads:[~2017-04-27  9:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 18:14 [PATCH 0/4] Reproducible binaries Juro Bystricky
2017-04-25 18:14 ` [PATCH 1/4] bitbake.conf: new variable BUILD_REPRODUCIBLE_BINARIES Juro Bystricky
2017-04-25 18:14 ` [PATCH 2/4] base.bbclass: initial support for binary reproducibility Juro Bystricky
2017-04-25 18:14 ` [PATCH 3/4] image-preling.bbclass: support " Juro Bystricky
2017-04-25 18:14 ` [PATCH 4/4] rootfs-postcommands.bbclass: " Juro Bystricky
2017-04-25 18:36 ` [PATCH 0/4] Reproducible binaries Martin Jansa
2017-04-25 19:24   ` Bystricky, Juro
2017-04-26  7:42     ` Martin Jansa
2017-04-26 16:43       ` Bystricky, Juro
2017-04-26 17:52         ` Martin Jansa
2017-04-26 18:22           ` Khem Raj
2017-04-26 18:33           ` Martin Jansa
2017-04-26 19:50             ` Bystricky, Juro
2017-04-27  9:50               ` Joshua Lock [this message]
2017-04-27 15:14                 ` Bystricky, Juro
2017-04-25 23:22 ` Trevor Woerner
2017-04-26  7:25   ` Patrick Ohly
2017-04-26 16:27   ` Bystricky, Juro

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=1493286610.26953.1.camel@linux.intel.com \
    --to=joshua.g.lock@linux.intel.com \
    --cc=juro.bystricky@intel.com \
    --cc=jurobystricky@hotmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.