On Dec 1, 2005, at 16:34, x nooby wrote:
> My repository has a single master directory called
> "svnrepo", and all my client directores are under
> that. For example:
> I am changing the server to use Apache/WebDAV, which
> seems to require a name for the repository. When I
> access my current repository via Apache, I have to use
> a URL like this:
I don't know what you mean when you say that Apache/WebDAV seem to
require a name for the repository. It seems like you have configured
Apache like this:
Thus saying that everything under the web path /acmerepos behaves
like a Subversion repository. You could just as easily use <Location /
> instead (assuming you have nothing else at data1.acme.com). So you
wouldn't actually have to change anything in the repo.
That said, having only a single top-level directory svnrepo inside
the repository doesn't seem like a very useful idea to me, so I'd
> I need to remove "svnrepo", and move it's contents up
> a level in the hiearchy, so client1 would be accessed
> like this:
> http://data1.acme.com/acmerepos/svnrepo (empty
> If I move the repos directories up a level, will the
> programmers be able to find them in the repo? For
> example should I do this:
> svn move svn://data1.acme.com/svnrepo/client1/* ..
> -m "moving svnrepos contents to highest level in repo"
> Then the programmers would do an update, and the
> working copies would still work? For example:
I don't think you can use the asterisk in that manner. As far as I
know, Subversion does not interpret any asterisk for you. The
asterisk only works because the shell expands it before the arguments
are passed to Subversion. In this case, the shell has no idea how to
expand an asterisk at the end of an svn:// URL.
You would need to execute one svn move statement for each directory
that you want to move. If you have very many directories and don't
want that many commits, you could pull down the entire repository
into a single monolithic working copy. But if you have many braches
or tags or very large projects then this might be prohibitive.
After you move the project directories in this manner, anybody who
has a working copy of those projects will have to execute an svn
switch command to switch the working copy to the new location.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Dec 3 07:03:17 2005