a few nits setting up svn...

Just set up a subversion repository with the notion it would be used
in production by a significant group of people for the first time. In
doing that, I noticed a few things I hadn't payed attention to before.

1) The template hooks don't mention anything about the directory that
   the hooks will be executed in, or the path that will be in effect
   when they run. This is annoying.
2) As a side effect of that, there is no error log that is kept for
   failures when running hooks. That means it is hard to debug the
   fact that you didn't realize that you had to
   /put/in/the/path/to/the/thing in the hook script.
3) There doesn't seem to be any documentation on appropriate
   permissions to give the repository parts. I'm using the svn+ssh
   access method, and right now I'm running with all the svn users in
   a group "svn" that can write everything under /svn, but surely this
   is overkill.
4) As an aside, it would be neat if one could make the ra_svn goo
   operate suid "svn" or something similar, so that the repository
   could be writable only to "svn" and accidents could be avoided.

-- 
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