On 04/11/2015 04:10 PM, Antonio Terceiro wrote:
> Nothing against the patch, but wouldn't it be better to handle this
> issue in one of the above layers such as debhelper, dpkg-dev, or
> something else? After all you are just setting an environment variable,
> and having to patch every single package out there is certainly not
> going to be sustainable.
> 
> $ grep-dctrl -F Build-Depends python-sphinx -n -s Package 
> /var/lib/apt/lists/http.debian.net_debian_dists_unstable_main_source_Sources 
> | wc -l
> 404
> 

I agree that it would be nice if debhelper or so already exported variables
like the build date. But different tools want to have the date in different 
formats
(in the patch I used the default format of Sphinx), or also want to have the 
time etc.

Patching packages would still be required to pass the date to the Sphinx call 
(some packages
I saw today call sphinx-build directly in d/rules instead of make).
We also hope that in the future more maintainers fix their packages when they 
see in DDPO
that it is unreproducible, which should then be more sustainable.

Regards,
 Reiner

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to