Windows project permissions

["Riechert, Gerald" <Ge...@specastro.com>]

I'm looking into migrating a Visual SourceSafe based project structure
to SVN and have a question about permissions. 

 

In VSS, various subprojects can be full access, read only or no access.
These permissions are set on a user and/or group basis. So, I may have
full access to subproject 1 and 2, read only on 3 and 4 and no access at
all on 5. The no access part is required.

 

Right now I'm thinking of just a flat file, network accessible
repository. Can a SVN repository be set up this way?

            

 

-- 

Jerry

 

 

 

Re: Windows project permissions

[Andy Levy <an...@gmail.com>]

On 2/16/06, Riechert, Gerald <Ge...@specastro.com> wrote:
> I'm looking into migrating a Visual SourceSafe based project structure to
> SVN and have a question about permissions.
>
> In VSS, various subprojects can be full access, read only or no access.
> These permissions are set on a user and/or group basis. So, I may have full
> access to subproject 1 and 2, read only on 3 and 4 and no access at all on
> 5. The no access part is required.
>
> Right now I'm thinking of just a flat file, network accessible repository.
> Can a SVN repository be set up this way?

Using the file:// access protocol, I don't believe so.  If you serve
via Apache2, (or, if you have svn 1.3, with svnserv), you can use the
"authz" file for per-directory access control. 
http://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4.2 -
This document is written for the Apache2 method, but from what I
recall seeing here the file format is the same when using svnserve;
someone more versed in 1.3 can fill in the details for pointing
svnserv at the config file.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org