Re: correctly using other packages in postrm
On Tue, Jun 01, 2010 at 01:13:28AM +0200, sean finney wrote:
> On Mon, May 31, 2010 at 12:24:48PM -0700, Steve Langasek wrote:
> > Does dbconfig-common know about all of these config files?
> > I think it's the responsibility of dbconfig-common to track them, and remove
> > them on purge. That way if your package is purged while dbconfig-common is
> > installed, the config file is removed, and if dbconfig-common is removed
> > before purge, a dpkg --purge dbconfig-common can still clean it up.
> i think in hindsight that's the way it *should* have been, but the
> documentation has suggested the contrary for long enough that i'm hesitant
> to break things, at least this late into the release cycle.
Hmm, what's the risk of changing it? I guess if dependencies are allowed to
be purged when a package depending on them is removed-but-not-purged,
dbconfig-common could obliterate config files that the depending package
expects to still have around. Is that the concern?
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/