On 11/7/06, Joseph Mocker <mock+svn@fakebelieve.org> wrote:
> I vaguely recall reading in the mailing list archives about this. From
> what I recall, there is no support for making a branch/tag read-only.
> The thread was in the context of creating a new feature that would allow
> you to "tag" files in a read-only manner. I forgot what the person had
> called it.
>
> I think you are on to an interesting approach with a hook script. So
> that you wouldn't have to modify the script for each new branch/tag,
> couldn't you just identify a set of operations that are allowed on say
> tags/, that only permit the "creation" of files, but not modification?
svnperms.py (http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/)
knows Create (calls it add), Update and Delete (calls it remove)
operations. Read can't be controlled by hookscripts.
So, with svnperms.py you can manage pretty much all CUD access
control. You could even have 1 user who *is* still allowed to UD the
tag.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 7 00:28:03 2006