Nixpkgs [1] uses SOURCE_DATE_EPOCH as well. We can reproducibly build the Python interpreter (and packages with [2]).
[1] https://github.com/NixOS/nixpkgs [2] https://bitbucket.org/pypa/wheel/pull-requests/77 On Fri, Mar 17, 2017 at 6:46 PM, Matthias Klose <d...@ubuntu.com> wrote: > On 17.03.2017 18:19, Robin Becker wrote: > > An issue has been raised for reportlab to support a specific environment > > variable namely SOURCE_DATE_EPOCH. The intent is that we should get our > time > > from this variable rather than time.localtime(time.time()) so that > produced > > documents are more invariant. > > > > First off is this a reasonable request? The variable is defined by > debian here > > https://reproducible-builds.org/specs/source-date-epoch/ > > > > What happens if other distros decide not to use this environment > variable? Do I > > really want distro specific code in the package? > > > > In addition we already have our own mechanism for making the produced > documents > > invariant although it might require an extension to support externally > specified > > date & time as in the debian variable. > > > > In short where does the distro responsibility and package maintainers > boundary > > need to be? > > the reproducible-builds thing is not just a Debian thing, it's supported by > other distros and upstream projects. > > Matthias > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig