Ben Collins-Sussman <sussman@collab.net> writes:
> > 3. A configuration option (and/or command-line switch) to use
> > "_svn" instead of ".svn". This is also non-trivial, since a
> > baton holding this state has to make it down into the right
> > parts of libsvn_wc. This is one method where having the patch
> > in advance would be helpful. Perhaps there's a clean way to do
> > it with a global, but in general we try to avoid globals...
>
> PROS:
>
> - ASP.NET users have a convenient workaround for IIS: just
> set the runtime option.
>
> CONS:
>
> - ASP.NET working copies become non-portable (unless Unix
> clients temporarily set the runtime option, or unless a
> rename script is run over the wc.)
>
> - converting the dirname from a compile-time variable to a
> run-time is a bit of work. Not horrible, but not trivial either.
If we're going to go with a configuration option, then why not just let
the user name their Subversion administrative directory whatever in the
heck they want to. The default would be .svn, and if somebody wants to
use '___svn___admin_dir_ate_my_lunch' for their admin directory name,
well then, more power to them.
In any case, the more I think about this, the more I think that we
should just make it a config Option that defaults to .svn... we can
document (in the conf file and the book) it so that if people want or
need to name their admin dir something else, then they know that they
may have some difficulties doing some things (sharing wc's amongst users
being the main one).
-Fitz, perfectly content to let people shoot themselves in the foot :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 26 20:05:36 2003