<<<
>>>
debconf best practices
Lots of room remains in debconf for developers to do silly and
counterintuitive things from a UI perspective
- misuse of notes: NO! Use README.Debian
- inflated priorities: NO!
- if 99% of users hit enter, priority should be low
- sigils
- overwriting conffiles: NO! (policy violation even if you use
debconf)
- config files that say, "don't edit; run debconf" are ABSOLUTE
EVIL!
- don't be overly verbose
- don't be too terse
- don't refer to the UI
- don't put several unrelated items into one note
- don't bother with debconf if there is an acceptable default
value and the config file can be edited later