If SOURCE_DATE_EPOCH is set, use it for manpages
commit22c5672f9e02f6947bbfd4041636ddbd271d1df5
authormhagger <mhagger@be7e6eca-30d4-0310-a8e5-ac0d63af7087>
Sat, 30 Jul 2016 10:47:02 +0000 (30 10:47 +0000)
committermhagger <mhagger@be7e6eca-30d4-0310-a8e5-ac0d63af7087>
Sat, 30 Jul 2016 10:47:02 +0000 (30 10:47 +0000)
treee35c4613644708c8c14723d185574cb75367973c
parente4e1eeeab8a89bafb5f0e7578451a98890893745
If SOURCE_DATE_EPOCH is set, use it for manpages

To improve build reproducibility, use the value of the environment
variable SOURCE_DATE_EPOCH as the date to embed in manpages if it is
set, rather than unconditionally using the current date. The idea is
that packaging systems can feed in the date of the last source
modification, so that the result is the same no matter when the package
is built. See the SOURCE_DATE_EPOCH specification [1] for more
information.

This was reported as Debian bug #831066 [2].

[1] https://reproducible-builds.org/specs/source-date-epoch/
[2] https://bugs.debian.org/831066

Suggested-by: Chris Lamb <lamby@debian.org>
git-svn-id: http://cvs2svn.tigris.org/svn/cvs2svn/trunk@5465 be7e6eca-30d4-0310-a8e5-ac0d63af7087
cvs2svn_lib/man_writer.py
cvs2svn_lib/run_options.py