Date: Fri, 21 Jul 2000 10:06:45 -0400 From: "Louis A. Mamakos" <louie@TransSys.COM> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: Will Andrews <andrews@technologist.com>, Marcel Moolenaar <marcel@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src Makefile.inc1 Message-ID: <200007211406.KAA53989@whizzo.transsys.com> In-Reply-To: Your message of "21 Jul 2000 10:54:03 %2B0200." <xzplmyvamok.fsf@flood.ping.uio.no> References: <200007192248.PAA23393@freefall.freebsd.org> <xzpya2xffvr.fsf@flood.ping.uio.no> <20000720233008.G28456@argon.gryphonsoft.com> <xzplmyvamok.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> Will Andrews <andrews@technologist.com> writes: > > On Thu, Jul 20, 2000 at 08:57:28AM +0200, Dag-Erling Smorgrav wrote: > > > This is arguably a bug in install(1), which should have an option to > > > save a backup copy. > > > > Umm, what about this: > > > > -c Copy the file. This flag turns off the default behavior of > > install where it deletes the original file after > > creating the target. > > > > Or perhaps I'm missing the point. :-( > > You are. Normally, install(1) moves the original file to its > destination. The -c option makes it leave the original in place, but > it still overwrites the destination. I want an option to make > install(1) make a backup of the destination file before overwriting > it. I seem to have a dim memory of install(1) on some system I used to use having a -u option to unlink the destination before installing to avoid the overwriting problem. Perhaps renaming and unlinking on success would be better. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007211406.KAA53989>