On 11/18/2009 07:58 PM, Richard W.M. Jones wrote:
Should just note here that dpkg is quite nuanced in how it removes
packages compared to rpm:
There are two states: normal removal of a package doesn't remove any
configuration files. That's so you can reinstall a package and not
have to reconfigure it. So called "purge" removes the configuration
files too.
I would think the same thing applies to removing generated data --
that there should be 3 states: remove just the package,
great, let's just ignore %config(noreplace) / %config
remove the
package and generated data,
I would be more than unpleasantly surprised if rpm -e mysql-server
would remove the databases as well (you know, I might just want to move
them to another server and I've started by removing the software first)
or rpm -e rrdtool would remove all the collected / processed data. And
so on, you get the drill.
That is, unless you teach rpm about "--purge" or something similar,
which should be neither default nor discussed on this list but in rpm's
upstream.
or remove the package and generated data and configuration files.
--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging
