> -----Original Message-----
> From: Stefan Sperling [mailto:stsp_at_elego.de]
> Sent: maandag 15 september 2008 23:57
> To: Garance A Drosihn
> Cc: Greg Stein; Talden; dev_at_subversion.tigris.org
> Subject: Re: Base text files, re: IRC chat
> On Mon, Sep 15, 2008 at 05:20:31PM -0400, Garance A Drosihn wrote:
> > At 8:48 PM -0700 9/14/08, Greg Stein wrote:
> >> There are basically three options:
> >> 1) at the root of the working copy, in a .svn subdirectory
> >> 2) in a subdir of ~/.subversion/
> >> 3) in a directory specified by your config (and/or an environ
> >> I'm leaning more and more towards making option (2) be the default
> >> because of the advantages of sharing text bases. At first, I was
> >> thinking (1) would be the default.
> > I'd think that (1) would be the better default. What happens if
> > multiple people might be using a single working copy?
> You could configure subversion to always do (1) in your system-wide
> (or per-user) Subversion configuration files. I presume we will be
> adding both command line switches and configuratoin file options
> to control this behaviour.
I would prefer (1) to be the default as it is the closest match to the old
behavior: the user chooses where the data is stored.
It provides most of the performance benefits of the new store without
changing how to use subversion.
I really wouldn't recommend using (2) as the Windows default. In many
corporate environments ~/ is in the roaming user profile. (Automatically
locally cached and sometimes automatically merged when a user logs on onto
different machines at the same time). And in most of these cases the size of
the roaming profiles is pretty limited (100 MB max at one of our largest
I can certainly think of scenario's where I would prefer (2) as option, but
I don't know a default windows location where non-admin users can always
write a lot of data. (I found %TEMP% in the per-user roaming profile at
# svn co http://example.com/path /wc/myproject/kiwi --metadata=c:/metastore
Example in one of the mails from Greg, looks pretty clean to me; allowing me
to optimize working copy at creation. And I think it is one of the few
variants that would be easy to implement in an existing GUI.
+1 on storing the reference in .svn/ below the working copy root.
Many of our AnkhSVN users use working copies on remote machines for websites
(sometimes shared). Defaulting to a local metastore would enhance their
performance by an order of magnitude, but would break using the same working
copy from different machines via different UNC paths.
I think we would have a lot of explaining to do, if we would break multiple
network paths to the same location in the default configuration.
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-16 00:35:39 CEST