From: Peter Maydell <peter.maydell@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Sphinx and docs/index.rst: dead code?
Date: Thu, 25 Jul 2019 10:08:55 +0100 [thread overview]
Message-ID: <CAFEAcA8eCsgAeX1--jZubKJ+v1U_ioa2q_Ec7UAQiRU6bKTpLA@mail.gmail.com> (raw)
In-Reply-To: <976a4589-f836-0f31-b682-f384e22149e9@redhat.com>
On Thu, 25 Jul 2019 at 00:22, John Snow <jsnow@redhat.com> wrote:
>
> Does anything actually use this file? It doesn't appear to be used for
> generating the HTML manuals.
It's there for if you want to do a "build all the manuals into
a single document" -- see the comments at the top of docs/conf.py.
Basically this is there because for QEMU's own purposes we want
to build several separate manuals (devel, interop, etc) so we
can install for the user only the ones that are user-facing
(ie "not devel"). But it seemed to me at the time to be worth
also supporting the "build a full thing" for the benefit of
sites like readthedocs. Currently the only way to use it is
if you hand-run an appropriate sphinx-build command.
(The fact that we will need to do some running of other
commands to autogenerate .rst input from .hx files might mean
that it's not really possible to support this sort of "third party
site" docs setup in the end; but for the moment we retain the
option to do this.)
Doing a top-level build will also complain about a couple
random .rst files in docs/ not being in the toc tree --
we need to fix this at some point anyway by putting that
documentation into its proper place in the manual set.
> It looks like we might use it for latex, man and texinfo output from
> sphinx judging by docs/conf.py, but I don't think we actually use sphinx
> to generate such output, so I think this is all dead code.
We will generate the manpage output in the same way we do
HTML, by invoking sphinx-build on the different manual
directories -- nothing in-tree does this today but this
patch:
https://patchew.org/QEMU/20190618104718.25433-1-peter.maydell@linaro.org/
does the conversion of the qemu-ga docs/manpage and should
be ready to go in once 4.1 is out the door.
thanks
-- PMM
next prev parent reply other threads:[~2019-07-25 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 23:22 [Qemu-devel] Sphinx and docs/index.rst: dead code? John Snow
2019-07-25 9:08 ` Peter Maydell [this message]
2019-07-25 16:34 ` John Snow
2019-07-25 16:42 ` Peter Maydell
2019-07-25 17:26 ` John Snow
2019-07-25 17:53 ` Peter Maydell
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=CAFEAcA8eCsgAeX1--jZubKJ+v1U_ioa2q_Ec7UAQiRU6bKTpLA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).