From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
Jani Nikula <jani.nikula@intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/7] doc-rst: generic way to build only sphinx sub-folders
Date: Fri, 19 Aug 2016 10:32:20 -0300 [thread overview]
Message-ID: <20160819103220.705274b0@vento.lan> (raw)
In-Reply-To: <20160818163514.43539c11@lwn.net>
Em Thu, 18 Aug 2016 16:35:14 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Sat, 13 Aug 2016 16:12:42 +0200
> Markus Heiser <markus.heiser@darmarit.de> wrote:
>
> > Add a generic way to build only a reST sub-folder with or
> > without a individual *build-theme*.
> >
> > * control *sub-folders* by environment SPHINXDIRS
> > * control *build-theme* by environment SPHINX_CONF
> >
> > Folders with a conf.py file, matching $(srctree)/Documentation/*/conf.py
> > can be build and distributed *stand-alone*. E.g. to compile only the
> > html of 'media' and 'gpu' folder use::
> >
> > make SPHINXDIRS="media gpu" htmldocs
> >
> > To use an additional sphinx-build configuration (*build-theme*) set the
> > name of the configuration file to SPHINX_CONF. E.g. to compile only the
> > html of 'media' with the *nit-picking* build use::
> >
> > make SPHINXDIRS=media SPHINX_CONF=conf_nitpick.py htmldocs
> >
> > With this, the Documentation/conf.py is read first and updated with the
> > configuration values from the Documentation/media/conf_nitpick.py.
>
> So this patch appears to have had the undocumented effect of moving HTML
> output from Documentation/output/html to Documentation/output. I am
> assuming that was not the intended result?
>
> I'm not sure that we actually need the format-specific subfolders, but we
> should be consistent across all the formats and in the documentation and,
> as of this patch, we're not.
Agreed. it should either use subfolders or not.
IMHO, the best would be to just output everything at
Documentation/output, if this is possible. That "fixes" the issue
of generating PDF files at the latex dir, with sounds weird, IMHO.
I guess I mention on a previous e-mail, but SPHINXDIRS= is not working
for PDF files generation.
Thanks,
Mauro
next prev parent reply other threads:[~2016-08-19 13:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 14:12 [PATCH 0/7] doc-rst: sphinx sub-folders & parseheaders directive Markus Heiser
2016-08-13 14:12 ` [PATCH 1/7] doc-rst: generic way to build only sphinx sub-folders Markus Heiser
2016-08-18 22:35 ` Jonathan Corbet
2016-08-19 11:37 ` Markus Heiser
2016-08-19 12:49 ` Jani Nikula
2016-08-19 15:52 ` Markus Heiser
2016-08-19 20:40 ` Mauro Carvalho Chehab
2016-08-19 20:43 ` Mauro Carvalho Chehab
2016-08-20 12:51 ` Mauro Carvalho Chehab
2016-08-21 12:02 ` Mauro Carvalho Chehab
2016-08-19 13:32 ` Mauro Carvalho Chehab [this message]
2016-08-13 14:12 ` [PATCH 2/7] doc-rst: add stand-alone conf.py to media folder Markus Heiser
2016-08-13 14:12 ` [PATCH 3/7] doc-rst: add media/conf_nitpick.py Markus Heiser
2016-08-13 14:12 ` [PATCH 4/7] doc-rst: add stand-alone conf.py to gpu folder Markus Heiser
2016-08-13 14:12 ` [PATCH 5/7] doc-rst: add docutils config file Markus Heiser
2016-08-13 14:12 ` [PATCH 6/7] doc-rst: parseheaders directive (inital) Markus Heiser
2016-08-13 14:12 ` [PATCH 7/7] doc-rst: migrated media build to parseheaders directive Markus Heiser
2016-08-14 18:09 ` [PATCH 0/7] doc-rst: sphinx sub-folders & " Jonathan Corbet
2016-08-15 8:21 ` Markus Heiser
2016-08-15 21:39 ` Jonathan Corbet
2016-08-16 18:22 ` Mauro Carvalho Chehab
2016-08-17 5:44 ` Markus Heiser
2016-08-17 6:26 ` Markus Heiser
2016-08-17 11:02 ` Daniel Vetter
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=20160819103220.705274b0@vento.lan \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
/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