[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Ambiguity In AuthzSVNAccessFile Permissions

From: Rob van Oostrum <rvanoo_at_gmail.com>
Date: Tue, 29 Jun 2010 16:51:21 -0400

On Tue, Jun 29, 2010 at 3:12 PM, Williams, James P2 (N-USA) <
james.p2.williams_at_lmco.com> wrote:

> Im unclear what directory permissions mean in my AuthzSVNAccessFile.
> For example,
>
>
>
> [/]
>
> goober = rw
>
> * = r
>
>
>
> [/trunk]
>
> tuber = rw
>
> goober = r
>
>
>
> who has permissions to create /trunk in this case? I want it to be goober,
> which is why I gave him rw in /. However, the read-only permissions he has
> in /trunk seem to also prevent his ability to create /trunk. Basically, I
> want him to be able to create the toplevel directories, like /trunk, but not
> edit their contents. Am I specifying it correctly? As written, the svn
> mkdir fails.
>
>
>
> Thanks,
>
>
>
> Jim
>
You can't get the behavior you're looking for using authz. You can configure
"create but not modify" permissions with svnperms.py which used to be part
of contrib. Couldn't tell you where it went since I last used it. Probably
someone else here knows.

-Rob
Received on 2010-06-29 22:53:01 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.