On Fri, Feb 11, 2011 at 10:10:40PM +0200, Daniel Shahaf wrote:
> 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.
Ah, OK. You're saying that nested repositories will never work because
it's not clear whether parts of a URL refer to a filesystem path to a
nested repository, or to a versioned path within the parent repository
of the nested repository. That's a good explanation for why people have
been asking about how the nested repository would be accessed.
I am, however, talking about something else in the part of my email
you've quoted. I said:
"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."
What I am saying is that the following should error out:
$ svnadmin create repos
$ cd repos/db
$ svnadmin create repos
$
just like this already does:
$ svnadmin create repos
$ cd repos
$ svnadmin create repos
subversion/svnadmin/main.c:600: (apr_err=165002)
subversion/libsvn_repos/repos.c:1393: (apr_err=165002)
svnadmin: E165002: 'repos' is a subdirectory of an existing repository rooted at '.'
Received on 2011-02-12 14:00:04 CET