I'll put my hand up as one of the confused...
I think a server-side config is needed. E.g. to
prevent the following scenario:
o Clients access the server using svn+ssh
o User A doesn't specify keyword expansion in his
config
o User B does specify keyword expansion in his config
o When User A adds a file (file A) to the repository,
keyword expansion is turned off for that file
o When user B checks out file A, keyword expansion is
turned off for file A.
Hence, someone is forced to run a script to turn on
keyword expansion for things in the repository if one
of the project members has added something while their
config is incorrect. This in turn implies that all
project members must make sure their config files are
kept in sync - very painful... A system wide client
config is only good if all the clients run on the same
machine, which we don't...
Dunk
--- Ben Collins-Sussman <sussman@collab.net> wrote:
> Others have been confused by this book text before.
> It's talking about
> a "system-wide configuration area" -- but not on the
> server -- it's
> talking about system-wide configuration on the
> *client* machine, as an
> alternative to setting up dozens of configuration
> areas for each user's
> homedir. Maybe we need to clarify that text
> somehow.
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail:
> users-help@subversion.tigris.org
>
>
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 22 01:49:56 2004