Robert Wenner wrote:
>Hi,
>
>maybe this should better go to the development list; however:
>
>For svn:// access, I want fine-grained access control (on a per-file
>basis) like WebDAV does.
>[Maybe the repository could even hide files the user has no access to.]
>Is this possible?
>
>WebDAV works as intended, but svnserve ignores the WebDAV users and access
>rights files.
>conf/svnserveconf does not seem to have a setting to specify the access
>rights file, and the format of the password database is different from
>the one used with WebDAV, so I think these won't work together out of the
>box.
>
>Google did not turn up anything useful.
>
>I looked into the hooks to implement this myself, but even if there were
>hooks for check out, this would feel like a quick and dirty hack.
>
>Is someone already working on such a feature?
>A quick look at the task list did not turn out anything in that direction.
>
>Any other comments on my problem?
>
>
We use svn+ssh:// here, and if you look in the hooks/ directory, you'll
see some nifty things.. like commit-access-control.pl &
commit-access-control.cfg.. that's how we restrict here.. coupled with
the hooks/pre-commit script! :)
My guess is, you could do something along these same lines--but be
careful about usernames & such.. there's a whole warning in the book
about using multiple access methods to the repositories... be sure to
watch out for the caveats! :) In the print-version of the book it's on
page 131 "Supporting Multiple Respository Access Methods"
Best,
--Glenn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jan 22 00:07:33 2005