![](https://seccdn.libravatar.org/avatar/5b748275c3dbb1ceee18ed554486547d.jpg?s=120&d=mm&r=g)
On Monday 2024-04-08 14:14, Andrei Borzenkov wrote:
On Mon, Apr 8, 2024 at 2:44 PM Johannes Kastl <mail@johannes-kastl.de> wrote:
Hmmm. Not sure if it is a good idea to remove the handcrafted config file just because the package is being uninstalled. But of course, now that I think of it, once the RPM got uninstalled rpm will no longer show a file as belonging to this RPM, either.
This is one thing dpkg does better. It distinguishes between "uninstall" and "purge". "uninstall" keeps (modified) configuration files and "purge" wipes them out. I wonder if this was ever considered for RPM.
install freeswan uninstall freeswan (/etc/ipsec.conf remains, being tracked as belonging to freeswan) install strongswan uninstall strongswan Now what: Do you associate ipsec.conf with freeswan or strongswan? Both? Neither? (Someone has probably made a choice in the apt implementation to solve this conundrum one way or the other. -- And RPM chose its solution to just not bother with purge tracking.)