Package: ucf
Version: 2.007
Severity: wishlist
Hi,
when an ucf-conffile is renamed or removed, the old file stays around
if one uses the naive approach mentioned in ucf's documentation and
the example maintainer scripts. Local intelligence is needed to have
the files removed:
* Have a list of ex-conffiles to manually process them on postinst
and probably postrm.
* Have a mechanism to leave them alone if they have been manually
changed
* determine manual change
* Ask the user whether to delete the changed ucf-conffile on purge
* Have a mechanism to specify defaults for this question to
prevent it from being asked on pool systems
I am not yet sure about how ucf could support this, but at least the
docs should mention this challenge, and the package should probably at
least ship example code showing how to handle this in the maintainer
scripts. However, I'd prefer ucf to handle this in ucf code, since it
is almost impossible to fix bugs in example code which will probably
be copied into random maintainer scripts a gazillion of times.
If you want to discuss ways how to do this, I'm eager to participate.
Greetings
Marc
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages ucf depends on:
ii debconf [debconf-2.0] 1.4.72 Debian configuration management sy
Versions of packages ucf recommends:
pn debconf-utils <none> (no description available)
-- debconf information excluded
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
