Date: Thu, 29 Jul 1999 14:17:24 +0200 From: Christoph Splittgerber <chris@sdata.de> To: "Wood, Richard" <rich@ruh-bath.swest.nhs.uk> Cc: "'Andrej.Brodnik@IBC.IskraSistemi.Si'" <Andrej.Brodnik@IBC.IskraSistemi.Si>, freebsd-isdn@FreeBSD.ORG Subject: Re: overuninstall.sh and i4b_rbch_ioctl.h Message-ID: <37A04654.7E21E941@sdata.de> References: <930BFA16390CD3119E010000F6E660C9A55E@fear.ruh-bath.swest.nhs.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
"Wood, Richard" wrote: > > > -----Original Message----- > > From: Andrej Brodnik [mailto:brodnik@IBC.IskraSistemi.Si] > > Sent: 29 July 1999 12:59 > > > <snip> > > $RMCMD $1 > > if [ -e $1-BACKUP ] > > then > > echo "moving $1-BACKUP" > > echo " back to $1" > > But that would remove the original file even if there was no backup to > replace it with, which is not the desired result. The way I see it, it is exactly what has to be done. > > overuninstall.sh only backs out changes made by overinstall.sh, i.e. it > checks to see if a -BACKUP is available, and if so, removes the original and > replaces it with the -BACKUP version. > If there is no -BACKUP version, the file has not been upgraded with > overinstall.sh and therefore there is (or there should be) no change to back > out. False, overinstall.sh installed the new file, the reason there is no -BACKUP is because the the file did not exist in the previous release. In this case, overinstall.sh has to remove the file regardless if there is a -BACKUP or not if it wants to undo the changes that overinstall.sh made. Christoph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37A04654.7E21E941>