RE: Re: subversion security, everyone can commit, limited to who can delete

Because what is being asked for is the duty of a manager, not the role of a vcs. "If you delete this file once, you're getting a talking to. Twice, you're written up. Third time, you're out of here."

Although I do think Frank is right in that a pre-commit hook is probably the best way to go about it.

Dale

-----Original Message-----
From: Frank Gruman [mailto:fgatwork@verizon.net]
Sent: Friday, October 14, 2005 1:31 PM
To: users@subversion.tigris.org
Subject: Re: subversion security, everyone can commit, limited to who
can delete

hmmm - curious.

Well - then I think I am going to have to throw you back to the list in
general to try to find a way to write a pre-commit hook script that will
try to evaluate a 'Delete' action.

While I was typing this up, I noticed a separate note that came in about
trying to evaluate the reason why this would be necessary. While true
(the role of a VCS), I can see value in this request. It would be the
same as being able to set the read/write permissions in
AuthzSVNAccessfile. I'd rather keep 99 of my developers from deleting a
file and only allow 1 to do it than have to try to find out what
happened to a file that I knew existed and then disappeared from the
repository. Sure - I could search the logs or go back and look, but why
not just prevent everyone from doing it to begin with?

Regards,
Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 14 22:50:07 2005