jre-phoenix wrote: > The problem described by Anton Zinoviev occurs more often: > When you install a package with aptitude or apt-get, then debconf will > run two times: > On the first run you are asked the questions. > On the second run the values from the configuration file are stored > into the debconf db.
On the second run, the config file does not yet exist. There are edge cases, such as a debconf question being added to a package that is already installed, where the config file may exist and the questions have not yet been asked, so the user would be prompted and then their answers written over with the values from the config file. > Still, I'm sure you had your reason to use a separate file > debian/config - so I'm not sure about any drawbacks for this solution. By doing this you eliminate preconfiguration, so the user has to wait around for your package to be installed before they can answer its questions. It would be better to test for the specific case where the config file already exists, and work around just that case. -- see shy jo
signature.asc
Description: Digital signature
