[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <042D234A-6B3D-43D4-84BA-8332C0596AA4@darmarit.de>
Date: Fri, 14 Jul 2017 19:35:59 +0200
From: Markus Heiser <markus.heiser@...marit.de>
To: Mauro Carvalho Chehab <mchehab@...pensource.com>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH RFC] scripts/sphinx-pre-install: add a script to check
Sphinx install
> Am 14.07.2017 um 18:49 schrieb Mauro Carvalho Chehab <mchehab@...pensource.com>:
>
> Solving Sphinx dependencies can be painful. Add a script to
> check if everything is ok.
just my 5cent:
What we need is a "requirements.txt" file to define a
**reference environment**. E.g. to stick Sphinx 1.4.9 in
such a reference environment::
<snip: requirements.txt> ---
Sphinx==1.4.9
sphinx_rtd_theme
<snap> ---------------------
The rest is similarly to what you wrote in doc-guide/sphinx.rst ...
The ref-environment can be build with virtualenv & pip::
$ virtualenv --python=python3 docenv
(doc-env) $ source ./docenv/bin/activate
(doc-env) $ pip install -r requirements.txt
>From now we can start our build as usual. If not already done,
first activate the environment::
$ . ./docenv/bin/activate
(doc-env) $ make htmldocs
This (requirements.txt) is the way python packaging goes.
Ok, this won't solve TeX installation problems of Linux distros,
for this a script like the one here in your RFC is helpful.
-- Markus --
Powered by blists - more mailing lists