[openstack-dev] Documentation containing external resource links & privacy breaches

Doug Hellmann doug at doughellmann.com
Tue Dec 8 13:19:17 UTC 2015


Excerpts from Thomas Goirand's message of 2015-12-08 13:31:57 +0100:
> On 12/08/2015 03:48 AM, Anne Gentle wrote:
> > 
> > 
> > On Mon, Dec 7, 2015 at 3:18 PM, Cory Benfield <cory at lukasa.co.uk
> > <mailto:cory at lukasa.co.uk>> wrote:
> > 
> > 
> >     > On 7 Dec 2015, at 18:37, Thomas Goirand <zigo at debian.org <mailto:zigo at debian.org>> wrote:
> >     >
> >     >
> >     > The reason why I'd like an env var, is that I could simply modify
> >     > openstack-pkg-tools (which is included in every debian/rules) to set
> >     > that variable once and for all. For example, just adding in
> >     > openstack-pkt-tools's pkgos.make:
> >     >
> >     > export OPENSTACKDOCSTHEME_SELF_CONTAINED=yes
> >     >
> >     > would do the trick for all my packages.
> >     >
> >     > Your thoughts?
> > 
> >     I am open to having such an environment variable that would control
> >     *all* documentation or theme related external properties, not just
> >     Google Analytics, but I’m also not a core on the openstackdocstheme
> >     project. ;)
> > 
> > 
> > One idea to consider, rather than all this extra configuration work can
> > you use one of the themes that ships with Sphinx for local builds? 
> > Anne
> 
> This would mean patching each and every OpenStack package to switch
> theme, which I am very reluctant to do. I'd prefer to find a single
> global solution with either a single patch, or even better, no patch at
> all and just an option through an env var.

The oslosphinx package forces it's theme to be the active theme. We
could make that configurable with an environment variable.

Doug

> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 



More information about the OpenStack-dev mailing list