[TSVN] Re: Complexity of relocate

Hello Lübbe,

sorry, that I couldn't reply earlier.

> I didn't follow everything you wrote, please excuse my lazness, but a short
> glance makes me think that you wanted to use 'switch' all the time, but used
> relocate instead. A wonder that your working copy still lives.

I just rechecked that and no, switch alone doesn't do the job:

  1. I created a local test repository with a file inside a folder.

  2. I checked out a working copy of the folder.

  3. I copied the repository to a new name (with the Explorer) and moved
     the folder into a newly created subfolder in this copy (with the
     Repo-Browser).

  4. Now I tried to switch the working copy from the old repository to
     the subfolder of the new repository and got the following error
     message:

       "Cannot replace a directory from within"

If I use relocate alone I get the same error message. Only the combination of
both does the job.

I think the steps 1 and 3 (replace copy with rename if you like) are an
absolutely normal proceeding while restructuring repositories, aren't they?

The more I think about it the more logic it is because the URL has changed (so
I have to relocate [even if the server part stays the same, it is another
repository]) and the folder inside the repository was moved (so I have to
switch my working copy to the new subfolder). But it isn't really intuitive
at first view that two steps are necessary.

Maybe this insight could help other people with the same problem even if there
is nothing TortoiseSVN can do about it.

By the way: If one made a mistake when relocating a working copy it seems to
be no problem to correct this with another relocate to the right URL.

> I also recommend to use a repository per project and not many projects in
> one repository. If the number of your projects increases this will work out
> better in the long run.

This is another point but good to know. Is there a rule of thumb which
maximum size a repository should have?

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.

Best regards
Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Feb 12 09:30:43 2005