Re: fine grained "access control"

> My organization needs the flexibility to allow/disallow locking, deletions,
> etc. on a per user or group basis. We run our server on a windows OS and
> will not be able to change this AFAIK.

That level of granularity will require server-side hook scripts.
Standard Subversion's authorization (authz) mechanism is only for
repository access, and only for read and write permissioning.
Anything else, as mentioned above, requires custom scripting.

Now...my question is "Why do you *need* these things?" Since
Subversion never actually deletes anything, you can easily undo a
delete if it was not permitted. As for locking/unlocking, the script
for this would be quite simple but again, why? Locks can be stolen if
need be. I'm not going to try and talk you out of this but before
going to great lengths to help, it makes sense to make sure your needs
aren't superficial first. If you can provide more details about
exactly what you need, and why, we can start the process of making
progress.

-- 
Take care,
Jeremy Whitlock
http://www.thoughtspark.org
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1192849
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].