660
Comment: don't redefine SOURCE_DATE_EPOCH if already available in the env
|
← Revision 6 as of 2015-11-17 12:20:09 ⇥
788
mention bug about supporting SOURCE_DATE_EPOCH in Pod::Man
|
Deletions are marked like this. | Additions are marked like this. |
Line 6: | Line 6: |
Get Pod::Man support SOURCE_DATE_EPOCH: see the bug Bug:801621. Otherwise POD_MAN_DATE is available to be set, see below. |
Manpages generated with the Perl module Pod::Man contain an embedded timestamp/date.
Solution
Get Pod::Man support SOURCE_DATE_EPOCH: see the bug 801621.
Otherwise POD_MAN_DATE is available to be set, see below.
Packages using debhelper
A fix needs to be done in debhelper. See https://bugs.debian.org/780259#40
Packages calling pod2man directly
Set the environment variable POD_MAN_DATE to the desired date.
E.g. in debian/rules add:
SOURCE_DATE_EPOCH ?= $(shell date -d "$$(dpkg-parsechangelog -SDate)" +%s) export POD_MAN_DATE = $(shell date -u +"%Y-%m-%d" --date="@$(SOURCE_DATE_EPOCH)")