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

Re: svn:external question

From: Enrico Straube <enrico.straube_at_cbb-software.com>
Date: 2004-11-26 16:26:06 CET

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

I think that it is impossible to realize that.

Enrico Straube
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:28:44 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.