[python-committers] build dependency on the branches on sphinx trunk necessary?
doko at ubuntu.com
Sun Jan 25 14:40:07 CET 2009
the requirement to build the documentation using a sphinx version from the trunk
was merged to at least the 2.6 branch. This is clearly not a bug fix. Is it
really necessary to rely on a trunk/unreleased version? Would it be possible to
revert this change?
Background: The Debian distribution requires distribution of files which can be
edited in the preferred format, which excludes generated documentation. I can
pre-build the 2.6 documentation, and then include it in the so called "contrib"
section of the archive, but I would like to see it available in the "main"
section. Including a copy of the sphinx trunk in the python package uploaded to
the distribution would be a hack around this (it is unlikely that the sphinx
trunk version will be available in Debian).
For python-2.5, Debian was not able to put the docs in the "main" section,
because a build tool with (in the eyes of Debian) "non-free" license was used to
build the docs. It is nice that this is fixed now, but for now one reason is
exchanged by another one why we cannot move the docs to Debian's "main" section
of the archive.
More information about the python-committers