Re: Restricted directory causes checkout to abort

Ben Collins-Sussman wrote:

>Doug Dicks <dwd-l@revelanttech.com> writes:
>
>
> In other words, don't nest
>restricted trees within non-restricted trees. Keep them separate.
>
>
In my scenario, the repository is

/a
/b
/c/restricted
/d

Are you saying that
/a
/b
/c
/restricted
/d

would be OK in general? It seems a checkout of the whole repo (/) would
have the same problem. So I get the "check out each directory one at a
time" solution, right?

Alternatively, I could set up a separate repository for the area I want
to secure. That's fine, if I have only a small number. But if I'm a
200 person company and I want to give everybody their own "private" work
area on the server, I have to set up 200 repositories.

IMO, it would be a very good feature for subversion to be able to handle
restricted access to directories and files. It would be very useful for
"enterprise" level adoptions as opposed to "workgroup" level adoptions.

Thoughts?

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 12 22:29:36 2003