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

Re: 'SVN' to '.svn' WAS: RE: Successful bootstrap on Mac OS X

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2001-09-04 18:39:49 CEST

> We've had this discussion before, and I believe the consensus was
> that the name of the administrative directory would be a run-time
> switch read out of a user's .svnrc. The .svnrc would give 2 or 3
> choices: "SVN", ".SVN", ".svn", or something like that.

The consensus was not universal. Allowing customization of the admin
directory makes it harder to write external tools such as vc-mode
(speaking of which, when we say that our administrative files are
supposed to be totally opaque, how do we expect vc-mode to operate?),
and also damages the portability of working directories between users,
as Scott points out.

Speaking of Scott, he wrote:
> I would strongly recommend a *per-directory* flag (which applies to
> subdirectories).

I don't like this idea either, because it still makes it hard to write
external tools, and because it creates a chicken-and-egg problem
regarding how to find the value of the per-directory flag.

Finally, I'm not very fond of hidden files, but the conflict between
the "svn" binary and the "SVN" directory in case-insensitive
filesystems may be sufficient reason to go with .svn, or at least a
name different from "SVN".

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:39 2006

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

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