Stefan Sperling wrote on Fri, Feb 11, 2011 at 21:10:20 +0100: > On Fri, Feb 11, 2011 at 07:16:24PM +0200, Daniel Shahaf wrote: > > Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100: > > > But I also think that the check for an existing repository should > > > work within any subdirectory of the repository, not just within the > > > top-level directory of the repository. > > > > > > Can you help by filing a DEFECT issue in our issue tracker > > > (http://subversion.tigris.org/issue-tracker.html) requesting that the > > > check be expanded to also work within subdirectories of a repository? > > > > Don't. It's already this way. Hyrum+I wrote it some time back. > > > > The reason? Because the URLs would be ambiguous: what should > > % svn info file://$PWD/path/to/dir/trunk | grep -i 'repository > > root:' > > print? > > What has this got to do with running svnadmin create within repos/db > or repos/hooks? > > Maybe you qouted the wrong paragraph and you were referring to > the ENHANCEMENT I mentioned that would allow creating nested > repositories? I've since changed my mind.
I was trying to say that nested repositories are blocked (at any depth-distance) because any URL referring to the deeper repository could also refer to the parent/ancestor repository, and there's no way to resolve the ambiguity.