Re: Packages' use of dpkg-statoverride
Matt Zimmerman wrote:
> What if the user has already configured a statoverride for the program, before
> even installing the package (or using an earlier version, etc.)? Should the
> config script even ask the question, or skip it?
I'd say skip it. dpkg-statoverride --list should prove useful here.
(OTOH, you man not want to skip it if the package is being
dpkg-recofigure'd (.config's $1 will == "reconfigure").)
> Also, should the statoverride be removed when the package is purged (as far as
> I know, dpkg doesn't try to do this)?
dpkg-statoverride --remove foo in the postrm, guarded on $1 = purge?
see shy jo