On 11/17/06, Thomas Harold <tgh@tgharold.com> wrote:
> Fabian Cenedese wrote:
> > Would it be possible, that if a text-base file is missing that svn
> > would check it out again? It knows the path and version, so
> > that shouldn't be a problem (unless the repository is not available).
> > If this is not possible could svn at least better cleanup and not
> > leave locks behind? Is there another command that would get
> > the text-base files but not overwrite the possibly modified real
> > files?
>
> I did something similar a few months ago (on a Gentoo system) where an
> automated script clobbered the contents of the .svn folder... and I
> agree that it's something that SVN needs to be better about dealing
> with. I found it to be very difficult to clean up after the .svn
> folders get slightly munged.
>
> (Maybe the upcoming changes in 1.5 might deal with strange local .svn
> folder issues in a more flexible fashion?)
No, svn doesn't just update the missing text-base, because to you it's
obvious that only the textbase is missing, but to svn the .svn area is
damaged. There's no way knowing if any of the other information is
correct or not. Better to let the user clean up the mess that was
created.
Also no: there's currently noone (I know of) working at relocating the
.svn area outside the working copy.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 08:46:57 2006