[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Problems changing config dir

From: Bridge, Peter <Peter.Bridge_at_dresdnerkleinwort.com>
Date: 2006-08-10 11:03:53 CEST

Hi Ryan,

Thanks for the info, maybe I didn't explain the problem well enough. The
problem is that svn seems to want to use config files located from my
windows %APPS_DATA% directory. In our case our profiles are running from a
network drive, a slow network drive. That means that svn has to access the
network drive every time it reads the config files. This wouldn't be so bad
apart from the fact that this problem cascades down through all the svn
clients we are using. So once we start dealing with a few thousand files
the config files are being accessed a few thousand times, and that is really
really slow for us. For example. Tortoise seems to share the svn config.
So what I was looking for was

> 'use this config directory for all svn commands'

Ie a registry setting, or local environment variable such as 'SVN_HOME',
that all svn clients would then know where to find the local config files.
I found some talk about adding a registry option for this, but not any
details if it was ever implemented. I did already find the command line
option you mentioned, but that is for a single command line call, and is
still a apin to have to specify every time.

Many Thanks


-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006c@ryandesign.com]
Sent: 04 August 2006 23:23
To: Bridge, Peter
Cc: 'users@subversion.tigris.org'
Subject: Re: Problems changing config dir

On Aug 1, 2006, at 12:47, Bridge, Peter wrote:

> I can't seem to change the config dir that svn uses (Windows).
> I've looked at registry stuff, global config options,
> command line option etc, but can't find a single place to say:
> 'use this config directory for all svn commands'

Check the help:

$ svn help commit
commit (ci): Send changes from your working copy to the repository.
usage: commit [PATH...]

   A log message must be provided, but it can be empty. If it is not
   given by a --message or --file option, an editor will be started.
   If any targets are (or contain) locked items, those will be
   unlocked after a successful commit.

Valid options:
   -q [--quiet] : print as little as possible
   -N [--non-recursive] : operate on single directory only
   --targets arg : pass contents of file ARG as additional
   --no-unlock : don't unlock the targets
   -m [--message] arg : specify commit message ARG
   -F [--file] arg : read data from file ARG
   --force-log : force validity of log message source
   --editor-cmd arg : use ARG as external editor
   --encoding arg : treat value as being in charset
encoding ARG
   --username arg : specify a username ARG
   --password arg : specify a password ARG
   --no-auth-cache : do not cache authentication tokens
   --non-interactive : do no interactive prompting
   --config-dir arg : read user configuration files from
directory ARG


Not that I'm agreeing with you that you should be specifying an
alternate config directory, but that's how you do it.

The information contained herein is confidential and is intended solely for the
addressee. Access by any other party is unauthorised without the express
written permission of the sender. If you are not the intended recipient, please
contact the sender either via the company switchboard on +44 (0)20 7623 8000, or
via e-mail return. If you have received this e-mail in error or wish to read our
e-mail disclaimer statement and monitoring policy, please refer to
http://www.dresdnerkleinwort.com/disc/email/ or contact the sender.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 10 11:05:15 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.