PATCH: Re: pws-19 + all patches: ``cp -f'' not always supportes

["Bart Schaefer" <schaefer@candle.brasslantern.com>]

On May 27,  6:09pm, Andrej Borsenkow wrote:
} Subject: pws-19 + all patches: ``cp -f'' not always supportes
}
} Our cp does not support -f.
} 
} Is it possible to do without it?

On May 27,  8:14pm, Timothy J Luoma wrote:
} Subject: Re: pws-19 + all patches: ``cp -f'' not always supportes
}
} why not just use 'rm -f' before the 'cp'

Indeed, why not.

} I'm not actually clear on when the '-f' flag would be needed....

The file is a symlink?  Somebody else owns it, but the build directory is
writable by you?

I'm not sure why it needs to be "cp" though.  Why not "mv -f" instead?

However, this patch just does the "rm -f" thing.

Index: configure.in
===================================================================
--- configure.in	1999/05/29 10:02:04	1.20
+++ configure.in	1999/05/29 10:02:17
@@ -1298,7 +1298,8 @@
 
 dnl The standard config.status is missing some essential features.
 dnl So add them now.
-[cp -f $CONFIG_STATUS $CONFIG_STATUS.old
+[rm -f $CONFIG_STATUS.old
+ cp $CONFIG_STATUS $CONFIG_STATUS.old
 sed '1,$s@^\( *ac_file_inputs=\).*$@\1`echo $ac_file_in | sed -e "s%^%:%" -e "s%:\\([^!]\\)% $ac_given_srcdir/\\1%g" -e "s%:!% %"`@' \
  $CONFIG_STATUS.old >$CONFIG_STATUS
  rm -f $CONFIG_STATUS.old]

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com