Mark Phippard wrote:
> No, Subclipse deletes it. It does so because the svn checkout command
> will fail if it encounters a file/folder of the same name. Short of doing
> a check on every local file, we have no way to know if this is going to
> happen, so we clean out the project folder before we issue the checkout
would it be that hard to implement? could you just recursively list the
existing contents of the directory and do a corresponding 'svn list' on
the repository to compare? it wouldn't be much of a performance hit
because the local directory would almost always be a sparsely-populated
and not-too-deep new project. also, there are obvious short-circuits
that come to mind with such an algorithm.
> The enhancement that Subversion is considering is just making the checkout
> process overlay an existing file/folder. Another alternative is to
> preserve the existing file, but still create the pristine version. Either
> way would work nicely for us.
IMHO it would be much safer to use the above approach and let the user
decide on a case-by-case basis. the hardest part would be creating the
GUI for resolving the conflict.
Received on Thu Aug 4 04:26:28 2005