On 30 May 1997, Kai Henningsen wrote: > [EMAIL PROTECTED] (Tom Lees) wrote on 27.05.97 in <[EMAIL PROTECTED]>: > > > There are ways to avoid this. For example, modify dpkg not to include any > > line with "config=yes" in it in the md5sum of certain files. > > This is a troll, right?
Wrong. > Or maybe you have forgotten how conffiles are actually handled: > > (old=original install, new=this install, current=possibly edited version) > > If old md5 = new md5, ignore new file (package unchanged) > If old md5 = current md5, install new file (conffile was not edited) > otherwise, prompt (both changed) > > Your change would mean that in case 2, dpkg would have to figure out how > to put the variables from the old script into the new one. But, for a package which adds config info, the new md5 != the old md5. Therefore, it would ask! And for a package where old includes config lines, the pkgtool would be rerun to update info which was config=yes. Locally modified lines wouldn't be config=yes, so the md5 would be different. Therefore, unless the sysadmin forgets to modify "config=yes" (put a banner to remind them), it works. So:- non-cfgtool md5 != cfgtoolized md5: old md5 != new md5. local file not modified: update anyway to use new cfgtool version. local file modified: cfgtool md5 == cfgtool md5: old md5=new md5 local file "not modified" (enough) - install new THEN, update from cfg database. See, it does work. -- Tom Lees <[EMAIL PROTECTED]> http://www.lpsg.demon.co.uk/ PGP ID 87D4D065, fingerprint 2A 66 86 9D 02 4D A6 1E B8 A2 17 9D 4F 9B 89 D6 finger [EMAIL PROTECTED] for full public key (also available on keyservers) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .