Marko Kaening wrote:
>I read in the thread "SVN and Locks" about the additional property
>"svn:needs-lock", but this is not really the same like "watch on" in CVS,
>since clients can easily override such locks (the server seems to be
>powerless).
>
>Looks like one would have to write his own pre-commit (or whatever)
>scripts to achieve the same like CVS, doesn't it?!
>
>
The hook script you'd need is "pre-unlock". There is an example script
that is created anytime you create a new repository; part of that
example script shows how to prevent users from breaking locks if they
didn't create them.
However, I've found that when administering a Subversion repository,
rather than trying to think of all the ways users might do what you
don't want them to and try to enforce policies against those, it's
better to use it for a while (maybe in a test sandbox) and find what
issues actually arise. Is there really a need to prevent others from
breaking locks? What if someone sets a lock and forgets about it, then
leaves for a month? Do you really want that administrative headache?
I'm not trying to say it's a bad idea, just that it is possible to lock
a repository down so tightly that it becomes much more of a burden to users.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 13 18:52:59 2005