severity 511034 wishlist tags 511034 wontfix thanks hi carl,
aplogies for the delayed response...
this is the intended behavior in dbconfig-common. the main idea is that
often the database's contents may be desired/used even after the package
is removed. there also might be cases where for other reasons the package
needs to be temporarily purged, or the package is renamed and then the
old package is purged, or other such corner cases.
there's also a technical problem, which is that dbconfig-common can't
reliably run at postrm (purge) time, because dependencies can't be
ensured to be available (maybe there's a workaround for this though).
i know there's an argument for the converse, that databases should
be removed (on purge at least), but since i'm messing with other peoples'
data i'm more inclined to take a safer/more conservative approach.
dbconfig-common is also designed so that it should handle installation
and reinstallation on top of existing databases, or at least that's
the intention.
sean
--
signature.asc
Description: Digital signature
