Re: It's Huntin' Season
- To: email@example.com
- Subject: Re: It's Huntin' Season
- From: Manoj Srivastava <firstname.lastname@example.org>
- Date: Fri, 01 Feb 2002 16:53:24 -0600
- Message-id: <[🔎] email@example.com>
- In-reply-to: <[🔎] 20020201215553.GA4498@home> (Nicolas Boullis's message of "Fri, 1 Feb 2002 22:55:53 +0100")
- References: <20020128021606.GB14924@azure.humbug.org.au> <20020128062110.4B3A4352FC4@lyta.coker.com.au> <20020129202755.C8800@silly.cloud.net.au> <20020129194853.GA706@ivywell.screaming.net> <20020130022309.96A86195C1@mixed.globetrotter.net> <20020130223521.GB5163@ivywell.screaming.net> <20020131014139.0B63A180EA@mixed.globetrotter.net> <20020131183004.GA936@ivywell.screaming.net> <20020201021706.BB42E180EB@mixed.globetrotter.net> <[🔎] 20020201215553.GA4498@home>
>>"Nicolas" == Nicolas Boullis <Boullis.Nicolas@libertysurf.fr> writes:
Nicolas> Can't you test in preinst if this file is the one you shipped in the
Nicolas> previous version ov the package ?
You may not need to do it in preinst, since these files are
created/updated in the postinst (which is the reason they can't be
marked as conffiles in the first place).
If you look at the script I posted, the user is not asked any
questions if the file on the system is the same file that is
currently being shipped. In the general case, I think this is good
enough; if one cares, one can special case the md5sum of the last
non-conffile one shipped and check that, but I hate special cases.
If in any problem you find yourself doing an immense amount of work,
the answer can be obtained by simple inspection.
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C