From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jeremy Sowden <jeremy@azazel.net>,
netfilter-devel@vger.kernel.org, Philipp Bartsch <phil@grmr.de>,
Arnout Engelen <arnout@bzzt.net>
Subject: Re: [nftables PATCH] build: support SOURCE_DATE_EPOCH for reproducible build
Date: Wed, 28 Jan 2026 13:48:35 +0100 [thread overview]
Message-ID: <aXoFo8uNjMMLXvvI@strlen.de> (raw)
In-Reply-To: <aXoEvAQnTjh31ImG@orbyte.nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> > > Generating one time-stamp in the Makefile is a pain in backside. I have
> > > come up with a way to do it, but it's fiddly. Florian, Phil, would it
> > > suffice to generate the time-stamp in configure?
>
> I deliberately chose a build timestamp, not a configure one. In most
> cases it won't matter, but since one could defeat the stamp by
> recompiling after making changes without calling configure.
I don't think thats a concern. This is geared towards official
releases only (and catching possible issues on update path on
real deployments, not deveopment workstation).
So I vote for configure-time.
next prev parent reply other threads:[~2026-01-28 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 12:30 [nftables PATCH] build: support SOURCE_DATE_EPOCH for reproducible build Philipp Bartsch
2026-01-23 16:36 ` Jeremy Sowden
2026-01-28 2:29 ` Pablo Neira Ayuso
2026-01-28 12:44 ` Phil Sutter
2026-01-28 12:48 ` Florian Westphal [this message]
2026-01-28 12:50 ` Jeremy Sowden
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=aXoFo8uNjMMLXvvI@strlen.de \
--to=fw@strlen.de \
--cc=arnout@bzzt.net \
--cc=jeremy@azazel.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@grmr.de \
--cc=phil@nwl.cc \
/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.