Re: [Xen-devel] [PATCH 0/3] docs: User oriented documentation

[Ian Jackson <ian.jackson@xxxxxxxxxx>]

Andrew Cooper writes ("Re: [PATCH 0/3] docs: User oriented documentation"):
> The point of using virtualenv is to get a known-compatible set of
> dependencies. See docs/sphinx/requirements.txt in patch 1.

I don't think we need to have more curlbashware in the Xen build tree.
Sphinx 1.4.9 is what is needed according to the metadata in your patch
1.  It is in Debian stable.  Likewise your metadata says docutils 0.12
is needed and Debian stable has 0.13.1.

> Use of the distro-packaged versions of sphinx/rtd-theme/docutils may
> work, but can be very hit-and-miss.

On irc you wrote:

 11:39 <Diziet> Why on earth do we need [virtualenv] ?
 11:44 <andyhhp> in this case, because stretch has a known-buggy
                 combination of docutils and sphinx

That does not seem to be documented in your
docs/sphinx/requirements.txt.

Is the fix available in stretch-backports ?

I really don't want to install virtualenv on xenbits.  Nor do I want
anyone doing so ad-hoc in their filespace.  This is not an appropriate
approach to software distribution and management.  And yes, I know
that I am rejecting the underlying design principle of things like
virtualenv, NPM, etc.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel