Hi!

On Sun, 2016-05-08 at 20:41:28 +0200, Alexis Bienvenüe wrote:
> On Fri, 15 Jan 2016 22:28:12 +0100 <[email protected]> wrote:
> > The forth patch changes dpkg-buildpackage to set SOURCE_DATE_EPOCH to
> > the time of the latest debian/changelog entry if it hasn't been already
> > set, effectively making the timestamps recorded by dpkg-deb in the most
> > common build process deterministic.
> 
> The SOURCE_DATE_EPOCH support is now implemented in pdftex/xetex:
> SOURCE_DATE_EPOCH will only be used to set CreationDate and related
> meta-data in produced files, and if SOURCE_DATE_EPOCH_TEX_PRIMITIVES
> equals 1, then the TeX primitives year, month, etc. will also be set so
> that the \today command will refer to the date given by
> SOURCE_DATE_EPOCH. See the discussion starting at [1], the news [2] and
> the commit [3].
> 
> The \today command is widely used in packages documentation, and I think
> replacing its value with the last source modification date is
> meaningful. It will also help reproducibility. Therefore I suggest to
> also add those lines to scripts/dpkg-buildpackage.pl, along with
> 0004-dpkg-buildpackage-Preset-build-timestamp-to-latest-c.patch:
> 
> if (! exists($ENV{SOURCE_DATE_EPOCH_TEX_PRIMITIVES})) {
>     $ENV{SOURCE_DATE_EPOCH_TEX_PRIMITIVES} = 1;
> }

This is very non-generic, and package or subsystem specific, which
implies starting to do things like this would not scale at all.
Consider what would happen if every package expected their own flag to
be set by dpkg. So I'm afraid I'll not be adding this to dpkg, sorry.

You should key such changes simply on SOURCE_DATE_EPOCH instead.

Thanks,
Guillem

Reply via email to