On Tue, Sep 16, 2008 at 7:17 AM, Bert Huijben <bert_at_qqmail.nl> wrote:
>...
> It's just that none of these users use the CLI as primary client and getting
> all GUIs to pass the same config directory setting is not very likely. If
> they use --config dir they pass their own folder and not one shared with all
> other clients.
Interesting point. People using multiple, variant clients should be
careful to put their options into the same config directory,
preferably the default home location (rather than something a client
has set up).
>...
> By the way, doesn't your recommendation break our c library API contract?
No. The API is the contract, and will remain compatible per the guidelines.
> Someone linking to the 1.4/1.5 library doesn't expect us to store Gigabytes
> of data in their roaming profile when they only access a working copy on a
> network share.
That is not part of the API contract.
Regardless, I think for the element of "least surprise", we are going
to need to use the "wc root" storage location as the default. I was
hoping to make the home dir the default, but after this discussion it
seems there are too many "gotchas" with managing your working copies
that way. I don't think we'll be able to *quite* make it invisible
enough in the presence of different use cases out in the wild.
So. Initial release will use "wc root" as the default. We may decide
to change that in the future, if we can automate enough of the
repair/detection/etc of WCs.
Cheers,
-g
---------------------------------------------------------------------
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 19:39:24 CEST