Re: .svn vs _svn on VS.NET (ASP.NET)

Greg Hudson <ghudson@MIT.EDU> writes:

> On Tue, 2004-03-09 at 15:49, Ben Reser wrote:
>
> As a result of the second bullet point, it would be much easier for us
> to use an environment variable instead of a config variable. (And since
> many of us, myself included, favor doing nothing at all, we should
> really be looking for the easy hack here, not the elegant solution.) We
> don't use environment variables for most configuration, but we do in a
> couple of cases (SVN_SSH and SVN_EDITOR), so it wouldn't be totally
> unprecedented.
>

(delurking)

This sounds like a nice away around the problem. Here's another idea,
from someone not familiar with code.

a) When looking for the config directory, look for both .svn and SVN,
in a canonical order.

b) When creating a config directory, choose a preference based on
platform or configuration.

Cross-developers using cygwin should be a little careful which version
of svn that they use to create new work areas. But even if you make a
mistake, renaming the config directory won't break anything (assuming
all versions are up to date so that they look for both directories).

(I'm also interested in seeing some solution to this, since we have a
number of groups at work that are just getting involved in .NET
development, some of which are doing Web development. Advocacy for a
better source control system is difficult enough already.)

--
Dan Muller
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org