hi javier,

On Wed, Oct 20, 2004 at 05:05:18PM +0200, Javier Fernández-Sanguino Peña wrote:
> - leave data after purge? -> only ask during purge.
> - back up database before upgrade? -> only ask during upgrades. user should 
> be notified where to find backups and possibly how to restore.
> and other ' only ask during install'
> 
> All these questions should be made on configuration, but, obviously, only 
> once (when the package is first installed or on upgrade if the debconf 
> question was not previously there). Obviously, the _actions_, will be taken 
> on purge|postinst|preinst, but the question itself is made in advance the 
> first time the package is configured. You might want to clarify the table 
> and change 'only ask' to 'only done' (or acted upon).

actually, this was intentional.  it seemed to me that the general
consensus was that the purge question should be asked just before
they'd be acted upon.  in the case of the purge question, the
you're not guaranteed that the answer to the question will
still be there at purge time depending on when it was configured
and what's happened to the debconf cache since.  with the upgrade
question, it'd be just fine to ask in the pre-configuration, and
if you look in the pseudo code overview, that's exactly what i
proposed.

> Similarly, you want to change the pseucode in 'overview of 
> installation/removal process' since all the INPUT should be done in 
> configuration. For an example take a look at how the PostgreSQL does this 
> (purge on removal and backup on upgrade) for _all_ databases managed by it.

i'll take a look at this, thanks.


        sean

-- 

Attachment: signature.asc
Description: Digital signature

Reply via email to