Ben Collins-Sussman <sussman@collab.net> writes:
>> Well, the impact of the /etc/subversion dir should probably be a bit
>> better documented (and it might be good to provide sample contents for
>> it in binary installations...)
>
> What's unclear in the book?
The semantics of the directory. It isn't obvious that it impacts users
on the client machine only, and not on the server.
(By the way, in this era of single user workstations, that isn't
particularly useful. A way to set defaults *on the server machine*
would be a valuable addition in a future release, but for now, the
text was unclear to me the first time I read it.)
Perry
> Chapter 7 has a whole section that
> documents every variable in ~/.subversion/config, and even says:
>
> "In addition to the per-user configuration area, Subversion also
> recognizes the existence of a system-wide configuration area. This
> gives system administrators the ability to establish defaults for all
> users on a given machine. Note that the system-wide configuration area
> does not alone dictate mandatory policy.the settings in the
> per-user configuration area override those in the system-wide one, and
> command-line arguments supplied to the svn program have the final
> word on behavior. On Unix-like platforms, the system-wide
> configuration area is expected to be the /etc/subversion directory; on
> Windows machines, it again looks for a Subversion directory inside
> the common Application Data location (again, as specified by the
> Windows Registry). Unlike the per-user case, the svn program does not
> attempt to create the system-wide configuration area."
>
>
--
Perry E. Metzger perry@piermont.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 21 05:21:56 2004