John Hasler [u] wrote on 25/08/2004 17:23:
Frank Küster writes:
There are maintainer scripts that create different configuration files, or a different number of configuration files, depending on the existing settings on the installing computer - or depending on debconf answers.
Those scripts could remove the files they don't use.
Oh well, and if a debian user would create those files anew (but uses them for a different thing), dpkg would happily remove them when a package which could create them is removed or purged. No thanks ;-)
Also, there are a few scripts around which check wether the files on a system still match those in the installed packages, which would fail on these, too.
I think the only way is to really create a way for maintainer scripts to (de)register files with dpkg on the fly. Ideally, this could be a registration for files that are removed when the package is removed or files that are removed on purge only.
cu, sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
