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

Re: Is it possible to check out a part of the repository tree?

From: <caoqiuliang_at_crisen.com>
Date: 2004-05-20 06:00:54 CEST

> Set up an apache server and configure mod_authz_svn. It's all explained
> in chapter 6 of the book. When user B does a checkout of a large tree,
> he won't receive the folder that he's not allowed to access.

It is said every time when I update the permission configuration file, I
will have to restart Apache. Is this true?

Actually what I want to do is to implement a version control system like
SourceSafe, for which these seem to be two problems that I can not overcome.

1) The administrator of the version control system is allowed to update the
permission configuration file from his PC. So the upload and maintenance of
the file become important. Is this easy to do or not? Furthermore,
restarting Apache everytime may be impossbile in my case. Is there any way
to avoid this?

2) If the non-recursive checkout is impossible, then does this mean that the
user has to check out the entire repository the first time he access the
repository? The repository may be very large in my case. Checking out the
entire repository is technically possible but definitely not a good
solution, I think.

3) From the description in your mail, it seems to me that one can not check
out a subdirectory into an existing working copy. But in our version control
system, the permission of each user may change often. For example, user A
has the permission to the folder "Help" but don't have the permission to the
subfolder "ch". Then he can check out the content of "Help". But later he is
allowed to access the subfolder "ch". In this case, can the content of "ch"
be checked out under "Help" without any problem? In my case, checking out
the subfolder into a location other than the existing working copy is
impossible.

In a word, what I want my version control system to be is: check out a
folder when necessary and only when necessary. In the meanwhile keep the
local folder structure exactly the same as on the server side.

Thank you very much.

Qiuliang

----- Original Message -----
From: "Ben Collins-Sussman" <sussman@collab.net>
To: <caoqiuliang@crisen.com>
Cc: "svn-dev-list" <dev@subversion.tigris.org>
Sent: Wednesday, May 19, 2004 11:06 PM
Subject: Re: Is it possible to check out a part of the repository tree?

> On Tue, 2004-05-18 at 23:52, caoqiuliang@crisen.com wrote:
> > Hi,
> >
> > I have a question: Is it possible to check out a part of the repository
> > tree?
>
> Yes, just checkout any URL you wish. The URL can be as "deep" in the
> repository as you want.
>
> > svn co -N file:///h:/db/Help h:/myClient/Help
>
> Non-recursive checkouts tend to be extremely broken. At this time, you
> cannot do a non-recursive checkout of a tree, and then make
> sub-directories "appear" by checking them out. It's apparently
> something that CVS users do, but SVN currently can't handle.
>
> My advice to you at this time is to avoid the -N switch altogether.
>
> > What is the reason? What I want to do is to add the permission control
to
> > Subversion, in a similar way like SourceSafe. That is to say, a folder
is
> > visible to user A but invisible to user B. For doing this, I have to be
able
> > to control a part of a repository tree.
>
> Set up an apache server and configure mod_authz_svn. It's all explained
> in chapter 6 of the book. When user B does a checkout of a large tree,
> he won't receive the folder that he's not allowed to access.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-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 Thu May 20 06:01: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.