On Wed, Jul 03, 2002 at 05:09:53PM -0500, Karl Fogel wrote:
> Josef Wolf <jw@raven.inka.de> writes:
> > For this the Config::IniFiles module could be used. Even if not: to
> > build a parser for ini-files is a trivial task in perl. The real
> > question is: where should the config file go? In the conf-directory of
> > the repos? Is it guaranteed that commit-email.pl can access this file
> > on the local filesystem? Are the contents of this directory
> > dumped/loaded when the repos is dumped/loaded?
>
> How about: the location of the conf file should be passed to
> commit-email.pl on its command line.
Please note my last sentence. I think it would be a good idea if
the config (which is very close related to the repos) would be
dumped/loaded when the repos is dumped/loaded. Therefore I would
prefer to put it there. But of course, passing it on the command
line the admin could decide where to put it (and therewith whether it
would be dumped/loaded). Maybe it would be even better to split the
config into two parts: /path/to/repo/conf/foobar.ini would contain
stuff which is not related to a specific revision/branch like
email-adresses. /path/to/repo/conf-versioned/foobar.ini would contain
stuff which is closely related to a branch/revision like the
regression tests which need to be run. Both directories should be
dumped/loaded along with the repos.
> > BTW: Are there already config-files defined for the repos/conf
> > directory? Does any description exist on those files?
> I don't think there are any yet.
Maybe the time has come to fill them up. I have a long list of ideas
what we could put into those files ;-)
--
-- Josef Wolf -- jw@raven.inka.de --
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 4 00:44:41 2002