From: Markus Heiser <markus.heiser@darmarit.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Sphinx version dependencies?
Date: Fri, 20 Jul 2018 18:28:09 +0200 [thread overview]
Message-ID: <1cc801608a1e71b54fe97aae6f5ad2a0024e8e5d.camel@darmarit.de> (raw)
In-Reply-To: <20180720150402.GA32320@infradead.org>
Am Freitag, den 20.07.2018, 08:04 -0700 schrieb Christoph Hellwig:
> On Fri, Jul 20, 2018 at 09:30:33AM +0200, Markus Heiser wrote:
> > We have this discussion over and over again an I believe we will have it again
> > and again, as long as we do not change our POV .. building viewing formats is
> > an application not a part of the Kernel.
>
> Sorry, but this is complete and utter bullshit.
Maybe .. I'am not a Kernel developer .. I only try to help with the doc tool-
chain. But if I don't want to install anything from the web, the plain text
is not as bad.
>
> If that was the case we could skip all that RST stuff and just stick
> to text files. If we want fancy docs it better behave like the rest
> of the kernel and just works. python virtual environments are just
> not going to cut it as they lead to a long-term maintainance nightmare.
Really a nightmare? This is what I do on my ubuntu/debian box ... I do
prefer py3 so I installed *virtualenv-py3* once from distro's package
manager:
$ sudo apt install python3-virtualenv
To setup up a environment for building htmldocs:
$ python3 -m virtualenv py3env
$ ./py3env/bin/pip install -r ./Documentation/sphinx/requirements.txt
now I have all installed in the in the py3env folder. To build htmldocs
with:
$ SPHINXBUILD=./py3env/bin/sphinx-build make htmldocs
If the env is no longer needed:
$ rm -r py3env
-- Markus --
> --
> To unsubscribe from this list: send the line "unsubscribe linux-doc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-20 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180719181556.GA21435@thunk.org>
[not found] ` <20180719190400.GB4800@magnolia>
2018-07-20 7:30 ` Sphinx version dependencies? Markus Heiser
2018-07-20 13:12 ` Theodore Y. Ts'o
2018-07-20 13:45 ` Markus Heiser
2018-07-20 14:52 ` Theodore Y. Ts'o
2018-07-20 16:00 ` Markus Heiser
2018-07-20 16:44 ` Darrick J. Wong
2018-07-20 16:58 ` Markus Heiser
2018-07-20 17:10 ` Darrick J. Wong
2018-07-20 20:43 ` Theodore Y. Ts'o
2018-07-20 21:28 ` Markus Heiser
2018-07-21 10:38 ` Jonathan Corbet
2018-07-20 15:04 ` Christoph Hellwig
2018-07-20 16:28 ` Markus Heiser [this message]
2018-07-20 17:08 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1cc801608a1e71b54fe97aae6f5ad2a0024e8e5d.camel@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).