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

RE: Re: Administering SVN Repositories

From: <dkrobbins_at_micron.com>
Date: 2005-04-06 17:44:32 CEST

Let me explain this in more detail.

I have setup a location in the httpd.conf file like so:
<Location /svn/myrepos>
        DAV svn
        SVNParentPath c:/svn/myrepos
        AuthzSVNAccessFile /svn/conf/svn-access-file

I create a repository under that, like /svn/myrepos/project1 and
everything is great. However, if I create the repository in a
subdirectory beneath that, i.e. /svn/myrepos/subdirectory/project1, then
Apache cannot see the repository unless I add the following to the
httpd.conf file:
<Location /svn/myrepos/subdirectory>
        DAV svn
        SVNParentPath c:/svn/myrepos/subdirectory
        AuthzSVNAccessFile /svn/conf/svn-access-file

If those are the limitations, that's fine. If there is a way to
accomplish what I want to above without the added entry to the
httpd.conf file that would be wonderful.


-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Monday, April 04, 2005 7:26 PM
To: dkrobbins
Cc: users@subversion.tigris.org
Subject: Re: Administering SVN Repositories

On Apr 4, 2005, at 12:36 PM, dkrobbins@micron.com wrote:

> I've setup Subversion (utilizing Apache on Windows) for my company and

> started adding repositories. I've set things up so that each
> department has a directory, with repositories (projects) setup beneath

> that. Everything was going great, until someone requested a bunch of
> sub-directories with the repositories being buried within that
> directory structure, not at the top level. That brought on a few
> questions...
> Can you even do that using Subversion? I cannot seem to find a way to
> configure Apache to allow it.

'svn mkdir URL'? I don't understand.

> These users are former CVS and PVCS users, so they are used to
> revision numbers on a per archive basis. They fear making the
> repository at the top level and having several projects beneath that
> will lead to a huge revision number and make it impossible to rollback

> to a specific "good" version of the code should something go wrong.
> How do you mitigated that risk? I would assume by using tags? Any
> other ideas?

See the many threads on this list about this. This is a myth and
misconception. It's perfectly normal for many projects to coexist in a
repository. The global repository number is easily shared, and it's no
more or less difficult to 'track' a project. The histories of the
projects don't "mix" together, and nothing is any harder.

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 Wed Apr 6 21:45:41 2005

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.