I am looking for a simple solution to set read/write permissions on our
subversion repositories. Unfortunately, svnserve supports read/write
access control on the repository level only which is too coarse for our
project. On the other hand, the Apache solution allows authorization on
the file level. But setting up a web server is an absolute overkill in
One way out of this dilemma might be a hook script. In particular,
tools/hook-scripts/commit-access-control.pl.in looks interesting. I can
integrate it into hook "start-commit" but how about "update" operations?
AFAICS, "start-commit" handles only write operations. How can I control
"checkout", "export", and "update" operations made by some arbitrary
user that connects to our server?
Are there any plans to integrate fine-grained authorization directly
into svnserve? Technically, this does not seem to be too complicated. I
am sure that a simple, efficient authorization mechanism is a killer
feature for medium-size projects.
I hope you can enlighten me :-)
Received on Fri Feb 20 08:30:22 2004