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

Re: svnserve path base authz

From: Lieven Govaerts <lgo_at_mobsol.be>
Date: 2006-01-31 13:09:04 CET


the feature you describe can be seen as a special case of issue 2298:
Non-recursive directory access for mod_authz_svn
( since authz is now in svnserve also the issue should be applicable to svnserve
as well. )

FYI, I haven't seen any interest on neither the users nor dev list for this

I suggest you add your use case as a comment to issue 2298, so that if someone
wants to implement it, your scenario is taken into consideration.


> -----Original Message-----
> From: Llewellyn Falco [mailto:isidore@setgame.com]
> Sent: dinsdag 31 januari 2006 0:46
> To: users@subversion.tigris.org
> Subject: svnserve path base authz
> Hello,
> Really loving the path base authorizations with svnserve, but small
> issues i wanted to add to the issue tracker.
> suppose you have a path as such
> main / code / a
> main / code / b
> main / code / c
> main / code / d
> and you have a user that you want to be able to read a , write b and
> not see c or d you should be able to configure as such
> [project:/]
> user =
> [project:/main/code/a]
> user = r
> [project:/main/code/a]
> user = rw
> which does work! except, i can not then
> svn co svn://localhost/project
> because i'll get nothing, i need to checkout all 2 different projects,
> this becomes hard & confusing on many levels
> i would prefer, that a read or write (r, rw) on a path, would allow
> basic reading of the path to the directy.
> ie. user could see main/code/a but could not see main/resources.
> So what'd think, can i make an issue?
> llewellyn.

This message was sent using IMP, the Internet Messaging Program.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 31 13:10:58 2006

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.