From: Jani Nikula <jani.nikula@intel.com>
To: Markus Heiser <markus.heiser@darmarit.de>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
linux-media@vger.kernel.org
Cc: Markus Heiser <markus.heiser@darmarIT.de>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] doc-rst: support *sphinx build themes*
Date: Sat, 06 Aug 2016 19:41:49 +0300 [thread overview]
Message-ID: <87eg6126k2.fsf@intel.com> (raw)
In-Reply-To: <1470410047-9911-1-git-send-email-markus.heiser@darmarit.de>
On Fri, 05 Aug 2016, Markus Heiser <markus.heiser@darmarit.de> wrote:
> From: Markus Heiser <markus.heiser@darmarIT.de>
>
> Load an additional configuration file into conf.py namespace.
>
> The name of the configuration file is taken from the environment
> SPHINX_CONF. The external configuration file extends (or overwrites) the
> configuration values from the origin conf.py. With this you are
> able to maintain *build themes*.
>
> E.g. to create your own nit-picking *build theme*, create a file
> Documentation/conf_nitpick.py::
>
> nitpicky=True
> nitpick_ignore = [
> ("c:func", "clock_gettime"),
> ...
> ]
>
> and run make with SPHINX_CONF environment::
>
> make SPHINX_CONF=conf_nitpick.py htmldocs
I think I would try to accomplish this by using the -c option in
SPHINXOPTS, and loading the main config file from the "special case"
config file. I think it would be a more generic approach instead of a
specific framework of our own. *shrug*.
BR,
Jani.
>
> Signed-off-by: Markus Heiser <markus.heiser@darmarIT.de>
> ---
> Documentation/conf.py | 9 +++++++++
> Documentation/sphinx/load_config.py | 25 +++++++++++++++++++++++++
> 2 files changed, 34 insertions(+)
> create mode 100644 Documentation/sphinx/load_config.py
>
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index 96b7aa6..d502775 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -20,6 +20,8 @@ import os
> # documentation root, use os.path.abspath to make it absolute, like shown here.
> sys.path.insert(0, os.path.abspath('sphinx'))
>
> +from load_config import loadConfig
> +
> # -- General configuration ------------------------------------------------
>
> # If your documentation needs a minimal Sphinx version, state it here.
> @@ -419,3 +421,10 @@ pdf_documents = [
> # line arguments.
> kerneldoc_bin = '../scripts/kernel-doc'
> kerneldoc_srctree = '..'
> +
> +
> +# ------------------------------------------------------------------------------
> +# Since loadConfig overwrites settings from the global namespace, it has to be
> +# the last statement in the conf.py file
> +# ------------------------------------------------------------------------------
> +loadConfig(globals())
> diff --git a/Documentation/sphinx/load_config.py b/Documentation/sphinx/load_config.py
> new file mode 100644
> index 0000000..44bdd22
> --- /dev/null
> +++ b/Documentation/sphinx/load_config.py
> @@ -0,0 +1,25 @@
> +# -*- coding: utf-8; mode: python -*-
> +# pylint: disable=R0903, C0330, R0914, R0912, E0401
> +
> +import os
> +from sphinx.util.pycompat import execfile_
> +
> +# ------------------------------------------------------------------------------
> +def loadConfig(namespace):
> +# ------------------------------------------------------------------------------
> +
> + u"""Load an additional configuration file into *namespace*.
> +
> + The name of the configuration file is taken from the environment
> + ``SPHINX_CONF``. The external configuration file extends (or overwrites) the
> + configuration values from the origin ``conf.py``. With this you are able to
> + maintain *build themes*. """
> +
> + config_file = os.environ.get("SPHINX_CONF", None)
> + if config_file is not None and os.path.exists(config_file):
> + config_file = os.path.abspath(config_file)
> + config = namespace.copy()
> + config['__file__'] = config_file
> + execfile_(config_file, config)
> + del config['__file__']
> + namespace.update(config)
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-08-06 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 15:14 [PATCH] doc-rst: support *sphinx build themes* Markus Heiser
2016-08-06 16:41 ` Jani Nikula [this message]
2016-08-06 20:22 ` Mauro Carvalho Chehab
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=87eg6126k2.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@s-opensource.com \
/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