Re: .svn directories

> How does subversion know that metadata exists at all for the
> directory in any form? It could be an export. If you think this
> will remove the need for 'export', then how would you propose
> that the working copy information get "automatically" cleaned
> from the user-global metadata store?

It doesn't. I think the idea is to give a good descriptive error
message:

$ mv /path/to/workspace /path/to/other
$ cd /path/to/other
$ svn status
/path/to/other is not a valid working copy.
Meta-data not found - was this moved from a different location?

The error message wording can probably be improved, but the idea
is to inform the user what could have happened.

> More importantly, if there are multiple working copies of the
> same tree checked out, how would it know which one to migrate
> to? Even two different working copies - this scheme appears to
> only allows searching based on the file path, since there is no
> longer any identifiers present on the working copy.

Presumably, you wouldn't have two working copies in the same
location. In other words:

/path/to/wc1
/path/to/wc2
/path/to/wc3

are three distinct working copies, even if they are checked out
from the same repository path.

The only exception to this is if the ~/.subversion directory is
NFS shared and the /path/to/wc is identical on more than one
machine. In that case, you're better off embedding the ~/.svn
directories.

Kumaran

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 27 20:47:17 2003