From: Holger Levsen <holger@layer-acht.org>
To: reproducible-builds@lists.alioth.debian.org
Cc: Ben Hutchings <ben@decadent.org.uk>,
Michal Marek <mmarek@suse.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [Reproducible-builds] [PATCH] kbuild: Add support for SOURCE_DATE_EPOCH environment variable
Date: Mon, 26 Oct 2015 19:31:18 -0600 [thread overview]
Message-ID: <201510261931.27345.holger@layer-acht.org> (raw)
In-Reply-To: <1445906948.2395.82.camel@decadent.org.uk>
[-- Attachment #1: Type: Text/Plain, Size: 984 bytes --]
Hi,
On Montag, 26. Oktober 2015, Ben Hutchings wrote:
> It's aimed at all build tools. For examples, see:
>
> https://codesearch.debian.net/results/%5C%24SOURCE_DATE_EPOCH%20-path%3Adeb
> ian%2F/page_0
> https://codesearch.debian.net/results/getenv%5C%28%22SOURCE_DATE_EPOCH%22%
> 5C%29%20-path%3Adebian%2F/page_0
https://reproducible-builds.org/specs/source-date-epoch/ has a spec for
SOURCE_DATE_EPOCH.
According to
https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal#Reading_the_variable
the following Debian packages support it already:
debhelper (>= 9.20151004)
epydoc (>= 3.0.1+dfsg-8)
ghostscript (>= 9.16~dfsg-1)
help2man (>= 1.47.1)
sphinx (>= 1.3.1-3)
texi2html (>= 1.82+dfsg1-4)
plus we have patches for doxygen, docbook-utils, gcc, gettext, libxslt,
ocamldoc, qt4-x11, texlive-bin and txt2man.
(We are only tracking adoption in Debian packages but of course we aim for
upstream inclusion of this.)
cheers,
Holger
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2015-10-27 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 23:15 [PATCH] kbuild: Add support for SOURCE_DATE_EPOCH environment variable Ben Hutchings
2015-10-26 21:03 ` Michal Marek
2015-10-27 0:49 ` Ben Hutchings
2015-10-27 1:31 ` Holger Levsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201510261931.27345.holger@layer-acht.org \
--to=holger@layer-acht.org \
--cc=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=reproducible-builds@lists.alioth.debian.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.