On Sat, Apr 09, 2016 at 08:46:43PM +0100, Jerome BENOIT wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > or GAP packages whose the documentation format have not been upgraded since a > while. > Let be concrete, I have in mind GRAPE [1] whose the documentation is not > reproducible [2].
Yes, but hopefuly, future version of GRAPE will probably move to gapdoc and no more use convert.pl. > > So if the original has 'Februar 2010' as the date, then we should use > > 'Februar 2010' as the date string. > > I do not think this is compatible with SOURCE_DATE_EPOCH, unfortunately, > > because SOURCE_DATE_EPOCH will not be set to the right time. > > Is there a way around that ? > > Yes, set SOURCE_DATE_EPOCH in the d/rules file. > > > > I plan to use it that way: > > GAP_CONVERT_DATE="Februar 2010" /usr/share/gap/etc/convert.pl -c -n AutPGrp > > . ../htm > > where 'Februar 2010' is the data found in the original tarball. > > SOURCE_DATE_EPOCH=$(date -u -d "1 February 2010" +@%s) [...] > > may work. This approach has the advantage to be readable by a larger > number of Debian maintainer. I doubt it. The specification says that For packages using dh, debhelper (in our toolchain, see 791823) exports this variable during builds, so no changes are needed. CDBS (in our toolchain, see 794241) exports this variable during builds, so no changes are needed. As a last resort to be avoided where possible, package maintainers may set and export this variable manually in debian/rules: export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog -SDate)" +%s) so to me using SOURCE_DATE_EPOCH and setting it to "1 February 2010" would cause more confusion. (Also it is more fragile, your function 'sub reprodate' would need to set LANG=C) Think of GAP_CONVERT_DATE as a parameter given to convert.pl and not as an environment variable. Cheers, -- Bill. <[email protected]> Imagine a large red swirl here.
