Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (nike.apache.org: 209.91.128.19 is neither permitted nor
 denied by domain of kdeugau@vianet.ca)
Message-ID: <4D5434AC.8030208@vianet.ca>
Date: Thu, 10 Feb 2011 13:55:40 -0500
From: Kris Deugau <kdeugau@vianet.ca>
Reply-To: "users@subversion.apache.org" <users@subversion.apache.org>
Organization: ViaNet Internet Solutions
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US;
 rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
MIME-Version: 1.0
To: "users@subversion.apache.org" <users@subversion.apache.org>
Subject: Re: svnadmin create complains about subrepositories
References: <20110210161516.0a1cd5a6@trust.cased.de>
 <20110210155911.GN9097@jack.stsp.name>
 <1C539F7D-8DAD-48D7-B5E8-1C5853AEB1BA@ryandesign.com>
 <20110210190218.74ffff28@trust.cased.de>
 <CB4587DA62024B40B9F929ECF639210F2C7693970C@USALWEXMB4.infor.com>
 <20110210191937.1413a899@trust.cased.de>
In-Reply-To: <20110210191937.1413a899@trust.cased.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Fabian Richter wrote:
> To be frank: I dont see why I am not able to create nested repos

A Subversion repository, from the point of view of the filesystem it 
lives on, is intended to be (mostly) a black box that you interact with 
through the SVN repository access layer you've configured.

> or
> what you mean that they need to be peers...

You can have a set of repositories side-by-side like so:

/path/to/repo1
/path/to/repo2
/path/to/repo3

You can't put another repository inside another, *at the same filesystem 
level*, like so:

/path/to/repo1
/path/to/repo1/repo2
/path/to/repo1/repo3

You *can*, if you really want, add a filesystem location containing a 
SVN repository as content to an existing repository...  although how 
you'd access it usefully is another matter.

> You say a repo folder can have the content i need it to have. I need
> them to have other repos. To be sure we are talking about the same
> thing:
>
> /repos1
> /repos1/repos2
> /repos1/repos3

Can you expand on why you really need to do this?  Why can't you use 
folders in a single repository, or just leave /repos1 as a regular 
filesystem directory, that contains repositories?

To ask things a bit differently, does arbitrary content under the URL 
that leads to /repos1 need to be version-controlled (eg, /repos1/file1), 
or is all the version-controlled content one layer deeper 
(/repos1/repos2/file1)?

> something like that. And the comparison to mysql DB doesnt make sense,
> because in a dbms I am able to deklare multiple databases for the same
> server or "root" dir, thats what is apparently not possible for svn...

Well, when you create a MySQL database, the tabledefs at least all go 
into /path/to/mysqldir/database2 - you can't put them in 
/path/to/mysqldir/database1/database2.

Subversion is pretty much the same, except you as administrator have 
somewhat more control of the filesystem location of each repository; 
it's perfectly possible (if inadvisable unless you need to isolate repo 
groups) to put a couple of repositories under /path/to/repgroup1, and 
another group under /another/place/repogroup2, and a lonely one off by 
itself in /some/other/repo.

-kgd