[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/5] Sphinx reproducibility update

From: Ludovic Courtès
Subject: Re: [PATCH 0/5] Sphinx reproducibility update
Date: Sun, 03 Jul 2016 23:52:00 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)


Leo Famulari <address@hidden> skribis:

> Since version 1.4.0, Sphinx has respected the SOURCE_DATE_EPOCH
> environment variable for the timestamps it puts in generated
> documentation [0].


> This patch series updates Sphinx to the latest version, 1.4.4, and
> provides all the new dependencies. The final commit in the series
> requires the new Sphinx.
> Why propagate pytz and snowballstemmer? Otherwise, many packages that
> use Sphinx started failing due to pytz or snowballstemmer not being
> avaiable. Rather than provide pytz and snowballstemmer to all those
> packages, I propagated them from Sphinx itself. I can add pytz and
> snowballstemmer to the Sphinx users if desired.

Makes sense.

> With this change, many Python 2 packages will become reproducible, at
> least on a single machine; the only thing holding them back was the
> manpage timestamps.
> These changes will require 142 rebuilds, mostly of Python packages, but
> also of libreoffice (libreoffice seems to depend on *everything*) and a
> few others. If the patches are good, should they go to master or to
> another branch?

You could push them to ‘core-updates’ as a way to save a little bit of
build time.

Thank you!


reply via email to

[Prev in Thread] Current Thread [Next in Thread]