Frank Küster <[EMAIL PROTECTED]> wrote: > The problems with ucf are:
The most important reason, IMHO, was the one I forgot: You either loose a main assets of debconf, or you ask twice. Consider that in a new version of the package, a default answer to the debconf question changes, and people who upgrade should have a chance to know about this. If you parse the configuration file, anyway, you can then determine if it has the former, old default, and set the debconf question to unseen (or even display an additional note in advance). Subsequently, the postinst writes the answer into the file. If you do the same with ucf, the user will be asked by debconf, and a second time by ucf. If you use just ucf, and do not set the debconf question to unseen, the user only has the file and the comments in it, but not the (translatable) debconf questions. The double asking will also be triggered with dpkg-reconfigure. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
