On Thu, 2 Mar 2017 19:16:47 +0100 Markus Heiser <markus.heiser@xxxxxxxxxxx> wrote: > This is very easy, if we use a requiremts.txt file where we > stick the versions and run the sphinx in this build in a > virtualenv which is build up by this requirements.txt. > > https://pip.pypa.io/en/stable/user_guide/#requirements-files > > To summarize, I recommend a Makefile.sphinx cmd which does > something like: > > virtualenv output/myenv > source output/myenv/bin/activate > pip install -r requirements.txt > sphinx-build ... > > I guess this is something we should discuss with Jon, he > is also familiar with it virtualenv. That would perhaps make the build more reliable, but it would also make the build dependent on net access to PyPI, and that's not an idea I like a whole lot. We should be able to do a build without going out on the network. I'm kind of pressed for time, but will try to ponder on this more shortly... jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
