Re: How to backup a running script? and how to recoverout-of-sync file?

At 9:59 AM -0500 7/25/03, Cedric Williams wrote:
>I'm thinking that I can just revert to a version before the (prior)
>version that is stored in text-base/ and then make my changes to
>bring it up to date - but will that mess up the diff with the
>prior-to-current version? (I'm guessing yes)

Well, I think I'd start by checking out a fresh, new working copy,
and see what sort of state it's in. Then you can make your changes
as necessary. The problems here seem to be limited to the particular
WC.

But you've still got the more fundamental problem: it's not working
to "self-commit" a script if it has keywords to expand. I don't
think that's going to go away. Checking to see whether the file's
writable might be done, but it would only allow SVN to refuse the
checkin, which ain't necessarily what you had in mind!

I suggest one of these remedies, whichever fits your needs better:

* Don't put keywords into the checkin script (or, anyway, don't plant
the SVN prop that says to do that)
* put the commit script into another directory, so it's not committing itself
* It might work to translate the script into Python (Python is
compiled before running; maybe the source file would be released by
the time the commit actually runs--haven't tried this myself).
* don't use Windows;-) (Actually, even on Unix, I suspect you'd get
problems from self-commits every time the revision number changed
size. But you could fix this by wrapping the whole script body in
(). Again, untried ideas.)

>The other option I'm thinking is changing the "entries" file in .svn
>to have the checksum for the base file that it actually has - but
>would that cause further badness in the repository?

That sounds like a deeply bad idea.

-- 
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org