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

Re: access rights mechanism for the users with Apache + SVN

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-04-17 14:00:28 CEST

On 4/17/07, Swati Kulkarni <swati.lkulkarni@patni.com> wrote:
> Hi,
> I have defined per directory access in AuthSVNAccess file already. But, our
> project requires
> that we should give -
>
> 1) read , checkin ,checkout to the developers
> 2) read , checkin checkout , ADD, delete to the Module leaders
> 3) read ,checkin ,checkout ,ADD, distroy rights to admin, PL of the
> project.
> (This kind of rights assignment we used to have , when we were using VSS.)
>
> But, it seems Subversion + Apache does not provide such distinctly defined
> access mechanism for its users.

That's correct. SVN's "native" access control only provides read,
write (write covers add and delete as well), and no access.

BTW, there is no "destroy" in Subversion at all. You can delete, but
that only removes the item from the HEAD revision. If you want to
actually remove all traces of an item from the repository, you need to
dump the repository, remove the item, then reload the repository.

> Dont we have any alternative for this?

As I posted on the 14th, look into svnperms.py.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 17 14:20:58 2007

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