mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/3] barebox: add option for building barebox reproducibly
Date: Tue, 16 Oct 2018 21:13:05 +0200	[thread overview]
Message-ID: <20181016191305.4cidchdb7ph3qjxe@pengutronix.de> (raw)
In-Reply-To: <20181016171537.alfcjnaa73wezwfl@falbala.home.lespocky.de>

On Tue, Oct 16, 2018 at 07:15:37PM +0200, Alexander Dahl wrote:
> On Tue, Oct 16, 2018 at 10:57:20AM +0000, Baeuerle, Florian wrote:
> > SOURCE_DATE_EPOCH uses the ptxdist release number for the timestamp, thus the
> > timestamp changes with every ptxdist release. I'd prefer to *really* get the
> > same binary when the source code was not changed at all. A ptxdist version bump
> > has a high potential of not touching anything barebox related.
> > 
> > I also do not like mangling the barebox version into a timestamp, but I couldn't
> > come up with any better idea.
> 
> If I understood correctly, you want some timestamp which does not
> change, as long as barebox is not touched. Why not base it on the
> barebox version then? What would be the problem with that?

That's what his patch does. I'd like to have one timestamp for all of
PTXdist.

Michael


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-10-16 19:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 14:19 [ptxdist] [PATCH 1/3] host-faketime: new package Baeuerle, Florian
2018-10-11 14:19 ` [ptxdist] [PATCH 2/3] barebox: add option for building barebox reproducibly Baeuerle, Florian
2018-10-12  7:59   ` Baeuerle, Florian
2018-10-12 12:01   ` Michael Olbrich
2018-10-12 12:21     ` Baeuerle, Florian
2018-10-24  8:19       ` Michael Olbrich
2018-10-26 13:46         ` [ptxdist] [PATCH 0/2] Barebox reproducible build + ptxdist setup configuration Baeuerle, Florian
2018-10-26 13:46           ` [ptxdist] [PATCH 1/4] config/setup: make reproducible builds configurable Baeuerle, Florian
2018-10-26 13:46           ` [ptxdist] [PATCH 2/4] barebox: depend on HOST_LZOP Baeuerle, Florian
2018-10-26 13:46           ` [ptxdist] [PATCH 3/4] lzop: add patch that allows overriding mtime Baeuerle, Florian
2018-10-26 13:46           ` [ptxdist] [PATCH 4/4] barebox: add support for reproducible build Baeuerle, Florian
2018-10-12 12:28     ` [ptxdist] [PATCH 2/3] barebox: add option for building barebox reproducibly Baeuerle, Florian
2018-10-16  8:59       ` Michael Olbrich
2018-10-16 11:06         ` Baeuerle, Florian
2018-10-16 12:51           ` Michael Olbrich
2018-10-16 14:11             ` Baeuerle, Florian
2018-10-16 19:06               ` Michael Olbrich
2018-10-16 10:09   ` Michael Olbrich
2018-10-16 10:57     ` Baeuerle, Florian
2018-10-16 12:38       ` Michael Olbrich
2018-10-16 14:27         ` Baeuerle, Florian
2018-10-16 19:20           ` Michael Olbrich
2018-10-16 17:15       ` Alexander Dahl
2018-10-16 19:13         ` Michael Olbrich [this message]
2018-10-11 14:19 ` [ptxdist] [PATCH 3/3] barebox_mlo: add option for building barebox_mlo reproducibly Baeuerle, Florian
2018-10-11 14:43 ` [ptxdist] [PATCH 1/3] host-faketime: new package Roland Hieber
2018-10-11 21:30   ` Jon Ringle
2018-10-16  7:33     ` Baeuerle, Florian
2018-10-16  8:47       ` Michael Olbrich
2018-10-12  7:47   ` Baeuerle, Florian
2018-10-16  8:51     ` Michael Olbrich
2018-10-16 11:34       ` Alexander Dahl
2018-10-16 12:30         ` Michael Olbrich
2018-10-16  8:53 ` Michael Olbrich

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=20181016191305.4cidchdb7ph3qjxe@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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