[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: Branko Čibej <brane_at_xbc.nu>
Date: 2001-09-04 19:30:32 CEST

Greg Hudson wrote:

>>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?),
All such tools should use the svn command line directly. Unlike cvs, svn
does (will?) provide all the information needed by such tool.

>and also damages the portability of working directories between users,
>as Scott points out.
The wc library could recognize several alternatives, like RCS, which
looks for version files in "RCS/", ".rcs/" and "./".

If we /do/ provide a command-line option to name the admin dir, we
should also provide a command that renames all admin dirs in a working copy:

    svn --admin-dir='.#svn#' morph --new-admin-dir=SVN foo bar/baz

Yes, I mean that. We should *not* offer a script instead, because that
functionality has to be available on all platforms.

OTOH, an --admin-dir option could point to an out-of-wc tree of admin
dirs: --admin-dir='~/.svn-admin/*' ...

Brane �ibej   <brane_at_xbc.nu>            http://www.xbc.nu/brane/
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.