>Are we talking at cross-purposes or is the Subversion commit hook that
>can be used for path-based access control for svn+ssh being overlooked here?
>
> From /usr/share/doc/subversion-1.3.2/tools/hook-scripts which is an
>example config file for the supplied (example, but useful) Perl hook script:
>
>-----------------------------------------------------------------
>[Make everything read-only for all users]
>match = .*
>access = read-only
>
>[Make project1 read-write for users Jane and Joe]
>match = ^(branches|tags|trunk)/project1
>users = jane joe
>access = read-write
>
>[However, we don't trust Joe with project1's Makefile]
>match = ^(branches|tags|trunk)/project1/Makefile
>users = joe
>access = read-only
>-----------------------------------------------------------------
There is also a python hook called svnperms.py also with an example config file which yet more interesting, I think.
Dan
--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list
