Ray Johnson wrote:
> Ok - this is perhaps a dumb question but i can't for he life of me
> figure it out and the docs are not really helping me out.
> I want to set the global-ignores file to know about additional files
> to ignore. We do *not* want to use the Windows registry. Much easier
> for our Ops guys to back up and edit a file then poking around in the
> registry. Shouldn't be a problem as the docs state you can use an INI
> file to set this stuff up. But where the heck is the location of that
> The book simply states this:
> "...on Windows machines, it again looks for a Subversion directory
> inside the common Application Data location (again, as specified by
> the Windows Registry). Unlike the per-user case, the *svn* program
> does not attempt to create the system-wide configuration area."
> What the heck is the "common Application Data location"? Since svn
> apparently doesn't attempt to create the system-wide configuration
> area am I supposed to keep guessing until I find it? I'm sure I must
> be missing some clearer documentation somewhere. Can anyone help
> point me in the right direction?
Have you read your %APPDATA%\Subversion\README.txt file? All the file
locations are described there.
> BTW, while pounding my head on this I have some other questions thoughts:
> 1) Why isn't the config in an XML format? Even MS is (slowly) moving
> away from the crappy registry and .INI world...
Because there are some things XML is not appropriate for, e.g.,
modification with a text editor. We do not need more than two levels of
> 2) Can you not have a repository level config? For example, I may
> have Linux code in one repository and Windows code in another. I
> would like to set things like the editor-cmd differently based on
> repository. However, it seems like I must do it for all repositories
> or have each user set things up in user configs.
There is no repository-level configuration as yet, although it's in the
pipeiline. I'd like to point out though that "editor-cmd" is the sort of
setting you _don't_ want to configure per-repository, because it depends
on client machine configuration.
Unless of course you're a bank and can force each and every client PC to
be configured identically.
> 3) Can you override the diff-cmd somehow at the command line level?
> (I didn't see a way to.) Most of our users want to use a visual diff
> tool. However, we have some scripts in our build environment that
> obviously can't use a GUI tool. If I could add an extra argument in
> my automated scripts that would work...
Yes, there is a --diff-cmd and a --diff3-cmd command line option.
There's also --config-dir that you can use to change the directory from
which the config files are read for the current command.
There's also "svn help" which tells you all that, not to mention the
Subversion Book at http://svnbook.red-bean.com/. :-)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Apr 14 20:27:29 2004