Tim Moloney <moloney@mrsl.com> writes:
> > You could write a pre-commit hook that uses svnlook to determine which
> > paths were being modified. If the tags directory is being modified,
> > and if those mods were anything more than just the creation of a new
> > tag, the hook returns and error, and the commit doesn't happen. You
> > could even have the script send email to the would-be committer
> > saying, "I know what you tried to do, buck-o!"
>
> Thanks for the info.
No problem!
> I don't have it running perfectly yet but I do have a few
> comments for the archives.
>
> .../svn/subversion/libsvn_repos/hooks.txt is a good place to
> start. However, it needs to be updated to show the scripts in
> the <repos>/hooks directory, not the <repos>/conf directory.
Ah...good catch!
> It would also be nice to mention that the script has to be
> executable by the owner of the httpd process. This tripped me
> up for a little bit.
Well, technically it has to be executable by the owner of the process
accessing the repository, which in DAV-ish cases is the same as the
user that httpd runs as, but is not really true over RA-local.
I see that Karl did not note this as carefully as I've stated above in
his patch (though I didn't check the context of his addition to see if
it was talking only about Subversion as access via Apache).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 12 03:36:05 2002