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

AW: svn:external question

From: Felix Gilcher <gilcher_at_exozet.com>
Date: 2004-11-26 16:37:01 CET

Hi Enrico,

this is quite easily realized. For the less paranoid: give all developers read-only access to all repositories. The can use them as externals now. Give them read-write access to those repositories that they really need to work on. For the more paranoid: every time a user needs a certain repository as external, grant him access. This is more work to administrate but helps you to keep track of who is accessing which repository. Mod_authz_svn even allows you to restrict users to certain branches/tags or even directories.

The svn:externals definitions does not imply any permission to read the repository that it points to, which is a good thing. Remember that this property is set by the user and not by the admin, even though it is tracked by svn. Thus, if it would imply a read permission you could use it to give yourself read access to a repository that you're not even allowed to look at just by setting it as svn:externals. Permissions are only granted by the admin in the apropriate config file which depends on the access-method you use.



Felix Gilcher
it developer
Exozet Berlin GmbH
Rotherstraße 20
10245 Berlin
> -----Ursprüngliche Nachricht-----
> Von: Enrico Straube [mailto:enrico.straube@cbb-software.com] 
> Gesendet: Freitag, 26. November 2004 16:26
> An: Ben Collins-Sussman; users@subversion.tigris.org
> Betreff: Re: svn:external question
> On Friday, November 26, 2004, Ben Collins-Sussman wrote:
> >>> So, in your mod_authz_svn access file, have you made the 'calc'
> >>> project
> >>> unreadable by user A?  If so, then when he checks out 
> 'paint', the 2nd
> >>> (automatic) checkout of 'calc' should not happen.  What 
> happens when
> >>> you try it?
> >>
> >> The problem is that user A can't compile the project 
> 'paint' because
> >> of missing header and lib files.
> > Okay, then for user A, make 'paint' read-write, and 'calc' 
> read-only.   
> > What's the problem?
> The problem is, that we have different types of developer. Some of
> them are on every project so they have always read/write access and
> some user should only work on some project and have there read/write
> access. I want to prevent the user to change an external repository
> per default. All users should only have read access to external
> repositories.
> I think that it is impossible to realize that.
> -- 
> Regards,
> Enrico Straube
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 26 16:39:28 2004

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.