On Thu, 2010-12-23 at 16:54 +0200, Alan Barrett wrote: > Is there a way to prevent svn from creating a $HOME/.subversion > directory? I know how to make it put the directory in a different > location using --config-dir=/wherever, but I want to avoid creating > it entirely. I can't find an option like "--no-config-dir" or > "--config-dir=none". > > I have discovered an ugly workaround: If I set > --configdir=/nonexistent/nonexistent (giving the name of a directory > that does not exist, and whose parent also does not exist), then the > absence of the parent directory means that svn will be unable to create > the child directory. >
See: <http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1> Quote: Note that the system-wide configuration area does not alone dictate mandatory policy—the settings in the per-user configuration area override those in the system-wide one, and command-line arguments supplied to the svn program have the final word on behavior. ... Registry-based configuration options are parsed before their file-based counterparts, so are overridden by values found in the configuration files. In other words, configuration priority is granted in the following order on a Windows system: Command-line options The per-user INI files The per-user Registry values The system-wide INI files The system-wide Registry values I don't think there's a way to 'override' this because the whole purpose is to help the user on whatever platform they may be using. *My* suggestion (if you're bound and determined to accomplish this) would be to create a link for $HOME/.subversion which points to a non-existent location. That would essentially provide you the same functionality as your arg: --configdir=/nonexistent/nonexistent -- Eric M. Hudish "Free for only $99.99!"
