Stefan Kanarski wrote:
> 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
Renaming/Moving a repository isn't a task you do every day. Usually, the
repository resides on a server and only the server admin can do that.
And once that's done, you _must_ use relocate before you do anything
else. That's because your working copy doesn't point to the repository
anymore and you first have to 'attach' your working copy to it again.
> the folder into a newly created subfolder in this copy (with the
> Repo-Browser).
_Now_ you can use your working copy again (after you used relocate). And
now you can use the switch command.
> 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?
No, you shouldn't do that without a really good reason! See my comments
above.
> 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.
That depends. If you know the mistake you made when relocating, you can
correct it. But usually people don't even know that they misspelled the
new URL and just wonder why it doesn't work anymore. In that case, you
have to read the URL inside .svn\entries file and use that to find out
how to correct it.
> This is another point but good to know. Is there a rule of thumb which
> maximum size a repository should have?
It has nothing to do with maximum size of a repository. The only
limitation to the size is your OS, harddrive and maybe speed.
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).
> 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).
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. 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.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Feb 12 12:12:10 2005