Hi, Bernd Eckenfels <[EMAIL PROTECTED]> (27/05/2003): > On Tue, May 27, 2003 at 10:19:04AM +0200, Michael Zehrer wrote: > > I will provide more Information on this with the next upload, explaining > > the difference between fist creation/formatting of the sample storage and > > optional formatting with upgrades/reconfigure. > > the question is, if you need it at all: > > a) in fresh install -> format data files > b) on upgrade: if format is compatible do not format it > > -> only if the format is not compatible you may ask this. > > If you ask this question always "what should i do on a future update, if the > format is incompatible" this may be quite confusing. On the other hand, it > is better, cause then the decision can be remembered.
I strongly agree, the description of the oops/format is currently meaningless: * it should only be displayed if there are existing storage files. * I don't know about compatibility, but if the statement of Bernd is correct, it should only be displayed if formats are not compatible. * the extended description should then be rephrased to tell the user that existing storage files have been found on the system and that reformatting them will erase previous data. It should be introduced by explaining what are these storage files used for (i.e. what kind of data the user may not want to loose). Furthermore, in your postinst script, you echo: "storage file generated." Your debconf description should be consistent with this echo: * "storages files" (short description) is a typo. * "storage files" (long description): is there one or more storage file? For example, I would rephrase as following: _Description: Format oops storage file? Oops uses the file /var/spool/oops/storages/oops_storage to store the data used as... . Such a file already exists on your system and need to be reformatted in order for oops to work correctly. Reformatting this file will erase all the previous data stored in it. If you do not want to loose these data, you should not choose this option, backup this file, and regenerate it by running as root: . /usr/sbin/oops -z -c /etc/oops/oops.cfg Cheers, -- Thomas Huriaux
signature.asc
Description: Digital signature