> -----Original Message-----
> From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com]
>
> Okay, that probably means that you have little influence on what this
> external
> application does.
For the time being anyways, I have no control over this.
> > How can I resolve this with svn commands and avoid temp files?
>
> First option should be to tell the external tool not to touch files
(in
> particular the write-protected content of .svn) it doesn't know about.
> However, it might also be the other way 'round that Subversion should
not
> try
> to version the contents of that directory. It depends. Unconditionally
> removing write-protected content is a bug in that external application
> though.
Yeah well if wishes were fishes... My hands are more or less tied for
the time being.
> Then, an option is to not store generated files in the first place.
Some
> people frown upon that, exactly because it should be possible to
> regenerate
> the content from the existing sources. I have a partial opinion on
that
> and
> actually check in released binaries. I don't care for diffing those
> though,
> so I only make the tags and then add the binaries to the tags.
I agree completely here. In fact I'll also consider setting up the
ignore property to exclude the generated data.
> A third option is to work around it. You could e.g. automate the
manual
> workaround you described [...]
Yep, this is what I am currently doing. I was hoping there would be
some little trick to help me out but this suffices until the root cause
can be addressed.
Thanks for your response!
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 26 17:41:17 2007