Re: Removing self-managed conffiles?
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).
> Is that acceptable? Or is there anything easier, more elegant, more
> policy compliant?
Other than that it seems completely acceptable to me.