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

RE: svnadmin create complains about subrepositories

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Fri, 11 Feb 2011 11:22:33 -0500

> On Thursday 10 February 2011, Stefan Sperling wrote:
> > On Thu, Feb 10, 2011 at 07:02:18PM +0100, Fabian Richter wrote:
> > > Am Thu, 10 Feb 2011 11:24:09 -0600
> > > schrieb Ryan Schmidt <subversion-2011a_at_ryandesign.com>:
> > > > On Feb 10, 2011, at 09:59, Stefan Sperling wrote:
> > > > >> and can you please add an --force switch to
> > > > >> still being able to create Repositories within the path of
> another?
> > > > >
> > > > > That's a reasonable request, I think. Not a usual use case
> but why
> > > > > not?
> > > >
> > > > Really? What possible reason could exist for doing this? :)
> >
> > I have no idea, to be honest. But then again I'm not going to
> guess.
> > Maybe someone can present a good use case for this? Dunno.
>
> The only reason I'm aware of is that you want to make browsing
> easier when you
> have multiple repositories, as there is otherwise no way to do
> that. The idea
> is that you have a parent FS-dir that contains the parent repo. The
> parent
> repo FS-contains the child repos. Further, it has repo-directories
> for each
> child repository, too. Since SVN tries to walk the FS-path as far
> as possible
> for locating the repository. Therefore, a "svn ls parent" will show
> the
> repo-content of the parent's root but a "svn ls parent/child-x"
> will not show
> the repo-content of the parent's child-x subdir but show the root
> of the
> parent/child-x repository.
>
> In that light, I support the suggested "--force" option for people
> that
> really, really need it.

If I have a project that has child sub-project I really really want them to be in the same repository. Actually, I put all my projects in the same repository so I can browser them in "some" repository browser like T-SVN of ViewVC. We have multiple repositories but they are for different product groups that work on projects that have no relationship to each other what so ever. Even those could be in the same repository but seeing how path based auth slows things down it seemed to make more sense to give each product group their own repo.

BOb
Received on 2011-02-11 17:23:14 CET

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.