Why dont you control directory based access using the .htaccess? wouldnt
that be much simpler?
Regards,
Madan.
On Mon, Jun 30, 2008 at 11:41 PM, Peter Kennard <peterk_at_livingwork.com>
wrote:
> (forward to dev if they want this :)
>
> I just set up apache2-svn-dav based access control for a big project with a
> bunch of repositories and many directories.
>
> So I have a fresh perspective :)
>
> I have a big repository with a lot of directories.
> I want to give a contractor:
>
> - list access to "trunk/java"
> so they can get the list on eclipse "ImportProject" and click on them
> - defined "rw" or "r" access to a subset of "trunk/java/*"
>
> I had to allow "@group = r" on "trunk/java" for the list access
> I then had to *explicitly* state "@group =" for every directory which I did
> not wish to give them any access, since the parent gives a default "r" to
> all
> it's children.
>
> I would like to set it up so the default on subdirectories is "no access"
> so if someone adds a new one it doesn't default to readable until we set it
> so. Yet, I want them to have list access on the parent (which currently
> makes children default to readable) so they can click-navigate
>
> Upon thinking about this it seems the best solution would be to add "x" to
> the
> directory permissions and specifying "x" without "r" or "w", disallows read
> and write but allows the operations needed for a directory "listing" of it's
> children. So full access would be "rwx". for compatibility "r" or "w" would
> imply "x" by default.
>
> Peter K.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
Received on 2008-07-01 06:41:35 CEST