Re: providing sphinx3-* binaries

2017-10-04 Thread Thomas Goirand
On 10/04/2017 04:41 AM, Ghislain Vaillant wrote: > > > On 03/10/17 22:46, Thomas Goirand wrote: >> On 09/29/2017 01:08 PM, PICCA Frederic-Emmanuel wrote: >>> Hello guyes. >>> override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) >>> ^

Re: providing sphinx3-* binaries

2017-10-03 Thread Ghislain Vaillant
On 03/10/17 22:46, Thomas Goirand wrote: On 09/29/2017 01:08 PM, PICCA Frederic-Emmanuel wrote: Hello guyes. override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) nodocs or nodoc I alsa do something like this when there is extension

Re: providing sphinx3-* binaries

2017-10-03 Thread Thomas Goirand
On 09/29/2017 01:08 PM, PICCA Frederic-Emmanuel wrote: > Hello guyes. > >> override_dh_sphinxdoc: >> ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) > > nodocs or nodoc > > I alsa do something like this when there is extensions. > > override_dh_sphinxdoc:

Re: providing sphinx3-* binaries

2017-09-29 Thread Ghislain Vaillant
On 29/09/17 12:08, PICCA Frederic-Emmanuel wrote: override_dh_sphinxdoc: ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS))) nodocs or nodoc I alsa do something like this when there is extensions. override_dh_sphinxdoc: ifeq (,$(findstring nodoc, $(DEB_BUIL

Re: providing sphinx3-* binaries

2017-09-29 Thread Thomas Goirand
Hi Antoine, Thanks for your post. On 09/27/2017 12:29 AM, Antoine Beaupré wrote: > 6. there are currently packages depending on *both* python-sphinx and > python3-sphinx. for me, that makes no sense at all: there is a > single set of documentation files built in a package, and it must be

Re: providing sphinx3-* binaries

2017-09-28 Thread Antoine Beaupré
On 2017-09-28 19:59:12, Dmitry Shachnev wrote: > On Thu, Sep 28, 2017 at 08:27:20AM -0400, Antoine Beaupré wrote: >> > And moving Python 3 packages to /usr/bin/sphinx3-build or something like >> > that will mean diverging from upstream (see below). >> >> Note that we already diverge from upstream i

Re: providing sphinx3-* binaries

2017-09-28 Thread Dmitry Shachnev
On Thu, Sep 28, 2017 at 08:27:20AM -0400, Antoine Beaupré wrote: > > And moving Python 3 packages to /usr/bin/sphinx3-build or something like > > that will mean diverging from upstream (see below). > > Note that we already diverge from upstream in numerous places in Python, > first and foremost in

Re: providing sphinx3-* binaries

2017-09-28 Thread Antoine Beaupré
On 2017-09-28 01:03:27, Dmitry Shachnev wrote: > Hi Antoine, and thanks for the detailed mail! > > On Tue, Sep 26, 2017 at 06:29:05PM -0400, Antoine Beaupré wrote: >> We just had a short conversation on the #debian-devel IRC channel >> regarding the upcoming Python 2 EOL, in the context of the Sphi

Re: providing sphinx3-* binaries

2017-09-28 Thread Simon McVittie
On Thu, 28 Sep 2017 at 01:03:27 +0300, Dmitry Shachnev wrote: > On Tue, Sep 26, 2017 at 06:29:05PM -0400, Antoine Beaupré wrote: > > 1. there should be a more easy way to override SPHINXBUILD in > > quickstart-generated Makefiles. IMHO, that means SPHINXBUILD?= > > instead of SPHINXBUILD=

Re: providing sphinx3-* binaries

2017-09-27 Thread Dmitry Shachnev
Hi Antoine, and thanks for the detailed mail! On Tue, Sep 26, 2017 at 06:29:05PM -0400, Antoine Beaupré wrote: > We just had a short conversation on the #debian-devel IRC channel > regarding the upcoming Python 2 EOL, in the context of the Sphinx > packages. > > [...] > > So that's the first probl