[Dbconfig-common-devel] reconfigure tries to populate database again

[sean finney]

hi uwe,

On Tue, Jun 06, 2006 at 04:54:20PM +0200, Uwe Steinmann wrote:
> I would expect that the database is only populated when it was
> created but postinst tries to populate it even on a reconfigure.

that was actually my intention.  if reconfigured via dpkg-reconfigure,
this gives the admin another chance to reconfigure the application,
including database settings.  otherwise, things would be quite a bit
messier as the admin would have to purge and reinstall the package.

using the same database settings will understandably confuse it a bit.
it might even be able to be considered a bug, since doing
dpkg-reconfigure with a non-interactive frontend will lead to some mess.
this could arguably be applied to policy 6.2, in which case it's
something i really ought to fix.

i think the best way out of this would be to save a copy of the "old
settings" when doing a reconfigure, and if they haven't changed ask
an extra question like "settings haven't changed, are you sure?", which
defaults to no action.  feel free to open a bug on this.


	sean

-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20060606/59ed97f9/attachment.pgp