On Thu, Jul 13, 2006 at 08:14:06PM +0100, Philip Martin wrote:
> Malcolm Rowe <malcolm-svn-dev@farside.org.uk> writes:
>
> > On Thu, Jul 13, 2006 at 07:50:31PM +0100, Philip Martin wrote:
> >> maxb@tigris.org writes:
> >>
> >> > + # This little dance satisfies Cygwin, which cannot overwrite in-use files.
> >> > + if test -f "$1"; then
> >> > + mv "$1" "$1.old"
> >> > + rm -f "$1.old"
> >> > + fi
>
> So when running the script config.nice on Cygwin it's not possible
> simply to overwrite the file config.nice, because it's open, and
> although it's possible to delete config.nice that still doesn't allow
> the file config.nice to be written.
>
Yes, that's how Max explained it to me. The original config.nice doesn't
get deleted until the current invocation exits (regardless of when the
'rm' occurs). So we can rename it and write a new config.nice, then
queue the original for deletion.
> Is the rm optional, i.e., is renaming config.nice enough to allow a new
> config.nice to be written? If so then it would make more sense to
> delay the rm until after the new config.nice has been written.
>
We could delay the deletion, AIUI, but we'd then need another check as
to whether config.nice.old exists before we try deleting it.
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 14 00:06:56 2006