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

[TSVN] Re: Complexity of relocate

From: Stefan Kanarski <tortoisesvn_at_kanarski.de>
Date: 2005-02-13 00:58:19 CET

Hello Stefan,

> Renaming/Moving a repository isn't a task you do every day.

you are very likely right but it's a task you do the more projects you are
beginning to manage with subversion and you became aware that you haven't
started with the optimal repository names and layout right away. And based
loosely on Murphy: Wherever possible one puts his foot in it. :-)

What you described in detail is absolutely logical and in the meantime I
realized that too but it's not intuitive at first.

> The reason you should use a separate repository for each project is that
> the revision numbers are global per repository, not per project (because
> Subversion doesn't know what folder may be a separate project).

We have resigned to the fact, that revision numbers increase with every commit
and accepted that it is just an internal mechanism as the subversion FAQ
states.

> > There is a problem though: Creating repositories on an Apache powered server
> > needs direct administrative access to the server while creating folders for
> > new projects in existing repositories could be done with TortoiseSVN.
>
> Not really. There's a 'workaround' which I use at work: Apache is
> configured with the SVNParentPath directive (see our docs about that).

We are using it that way too.

> Then I have shared that folder with read/write access only for me. If I
> have to create a new project, I just go to that network folder and
> create a new repository.

Here is the point: The colleagues should be able to create new projects on
their own and not be dependant on me.

> Just remember: _never_, _ever_ access the
> repository via the network share, always access it via Apache. But just
> creating a repository via a network share is safe.

Is it safe even if one accesses a Samba based share on a Linux server with the
Windows based TortoiseSVN? I read in the subversion book that the Berkeley DB
environments aren't portable (svn-book_1.1.pdf page 66).

If the only problem is the repository wide revision number I think a few
repositories for a couple of projects in each is OK. But thank you very much
for your suggestions.

Best regards
Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Feb 13 09:14:51 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.