You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Stefan Küng <to...@gmail.com> on 2009/07/24 16:30:06 UTC

Re: Storing Subversion repositories within another Subversion repository.

On 24.07.2009 18:15, Phillip Dann.Ward wrote:
> It is an empty repository (i.e. empty branches/tags/trunk folders, etc)
> created using "svnadmin create".
> I intend to do absolutely nothing with this empty repository once it is
> in my development repository.
> I was just wondering if there might be any side effects of doing this
> such as the development repository getting 'corrupted' if Subversion
> gets confused by seeing the empty repository inside it or perhaps the
> empty repository not being exported properly because Subversion thinks
> that it is part of (rather than just simply stored in) the development
> repository.
> Phil.

It's not supported, so you should/must not do it. Think about it: 
whatever name you choose for the name of your 'internal' repository, 
you'll have to create a folder with that name inside the repository. But 
that repository folder is not for you to create files/folders - 
Subversion might one day use its own folder with the name you chose for 
your internal repository - then you're really, really screwed.

And: I can tell you right now that some svn clients will not work 
correctly with such a setup (I know for sure that TSVN doesn't).

So: don't do it.

Stefan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2375281

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Storing Subversion repositories within another Subversion repository.

Posted by Tyler Roscoe <ty...@cryptio.net>.
On Fri, Jul 24, 2009 at 06:30:06PM +0200, Stefan Küng wrote:
> On 24.07.2009 18:15, Phillip Dann.Ward wrote:
> > It is an empty repository (i.e. empty branches/tags/trunk folders, etc)
> > created using "svnadmin create".
> > I intend to do absolutely nothing with this empty repository once it is
> > in my development repository.
> > I was just wondering if there might be any side effects of doing this
> > such as the development repository getting 'corrupted' if Subversion
> > gets confused by seeing the empty repository inside it or perhaps the
> > empty repository not being exported properly because Subversion thinks
> > that it is part of (rather than just simply stored in) the development
> > repository.
> > Phil.
> 
> It's not supported, so you should/must not do it. Think about it: 
> whatever name you choose for the name of your 'internal' repository, 
> you'll have to create a folder with that name inside the repository. But 
> that repository folder is not for you to create files/folders - 
> Subversion might one day use its own folder with the name you chose for 
> your internal repository - then you're really, really screwed.

Wait, maybe I misunderstood.

OP, are you talking about sticking extra files into the repository
directly? Like alongside conf and db you add my_directory? If so, this
sounds dangerous and I really have no idea what you want to accomplish
with such a system.

If you want to do something like "svn add my_empty_repository_template"
and version that directory with Subversion, that should be fine (though
I'm still unclear on the use case).

tyler