An access permissions problem

Hi

We host each of our projects in a separate svn repo and control access permissions via Apache.

In one large project, we need to limit the visibility of a few confidential files. We have done this by specifying something like:

[myproj:/trunk/ConfidentialFolder]
@myPrivilegedGroup = rw
* =

The problem with this is that the confidential files become visible to everyone when we create a branch. Of course, we could control the visibility of the branches by adding further directives but this becomes complex and hard to validate. So we think it is best to only set access permissions on entire repositories.

Therefore, we think a better solution would be to put the confidential files in their own repo and bring them into the large project with an external. However, I am not sure what happens when an external can't be resolved because access to the external repo is denied.

I would welcome any advice on this problem.

BR

David
Received on 2010-12-21 15:47:29 CET