On Fri, Jan 19, 2007 at 09:43:04PM +0100, Santiago Vila wrote: > On Fri, 19 Jan 2007, Marc Haber wrote: > > I have a package with a bunch of configuration files that are managed > > by my maintainer scripts and not by dpkg. I now need one of them > > (a.conf) to vanish. > > > > How do I do this in a clean way? I am thinking about the following: > > > > (1) Let the new package version know about the md5sum of the last > > version(s) of a.conf that were in the package. > > (2) If one of the md5sums matches, the file has not been changed, > > remove it. > > (3) If none of the md5sums matches, the file has locally been changed, > > rename it to a.conf.package-old > > Instead of 1,2,3 you could do 1,2,3 only when upgrading from a version > previous than the one not having a.conf anymore, and in case > that (3) happens, keep a.conf untouched, instead of renaming it > (assuming the program will not read a.conf anymore).
Yes, that sounds sensible. It is, however, frustrating that there is no method (for example, offered by ucf) to do this without that much coding in maintainer scripts. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]