[viewvc-users] Configurable config file location?

Hello all,

First, some background. Where I work we've got ViewVC running at a few
different sites. We've got code changes (small ones, one of which may
have been incorporated upstream) and template changes at each site.

I'd really like each site to use exactly the same code, checked into our
source control system, but each site requires some config file changes
(I've got templates that make use of custom template variables).

As it stands I've got ViewVC checked into our source control system
(both as the uninstalled source and as the configured/installed version)
along with viewvc.conf.

My thought was that I'd change the code to allow the config file
location to be overridden by an environment variable. Looking at the
code it looks like there's already some kind of support for this. Is it
true that I only need to change all the places that define CONF_PATHNAME
to define it as "None"?

If so, I could then set VIEWVC_CONF_PATHNAME in the Apache config, and
have multiple "viewvc.conf" files, one for each site. This would
certainly be an advance.

_However_, what would be really lovely to be able to do in a
"viewvc-newyork.conf" would be something like:

==================================================================
include "viewvc-common.conf"

[config_section]
variable_a = blah
variable_b = blah
==================================================================

Unfortunately I'm not sure the ".ini" file format has any syntax for any
such usage. I could always do this myself with the C preprocessor, but I
don't think I really want to add the burden of having a Makefile that
utilises the C preprocessor.

What do you think?

Cheers,

John.

-- 
John Beranek                         To generalise is to be an idiot.
http://redux.org.uk/                                 -- William Blake

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2635353

To unsubscribe from this discussion, e-mail: [[email protected]].