Package: ucf
Version: 3.0036
Severity: normal
When dealing with a lot of prompts, as in the course of upgrading many
machines to a new Debian version, it becomes apparent that ucf's dialogs
are not as well designed as dpkg's.
Compare:
| ┌─────────────────────────┤ Configuring openssh-server
├──────────────────────────┐
| │ A new version (/tmp/fileYPaJmB) of configuration file
/etc/ssh/sshd_config is │
| │ available, but the version installed currently has been locally
modified. │
or
|
┌────────────────────────────────────────────────────────────────Modified
configuration
file───────────────────────────────────────────────────────────────────┐
| │ A new version (/tmp/filefZxy2t) of configuration file
/etc/default/bacula-fd is available, but the version installed currently has
been locally modified. │
| │
│
| │ What do you want to do about modified configuration file
bacula-fd?
│
with
| Configuration file '/etc/init.d/stunnel4'
| ==> Modified (by you or by a script) since installation.
The dpkg prompt immediately makes it clear which file we're talking about. On
first glance.
UCF's prompt first gives me more useless info, like the package (if I'm
lucky!), and even the temporary location of the newly suggested file.
Only in the course of the running text do I actually learn the thing I
care about -- the name of the file in question.
The filename really should be in the title of the prompt and (/or) as the very
first thing in the very first paragraph.
Thanks,
Peter
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/
