man zypper: “… The remove command will uninstall the selected and their dependent packages. …”
To me this means that zypper remove will remove all files which were part of the package(s) and it will not remove anything else (e.g. files, which the package(s) created while it/they were installed because those were not part of the package(s))
So the command does exactly what the manual says. Why should the openSUSE documentation compare zypper remove with apt purge (or any other package managing tool)? This would not be very helpful to me because I do know nothing about apt.
RPM does not have notion of separate steps “remove” and “purge” like DPKG. RPM package removal removes all files listed as part of package. RPM leaves a copy of modified configuration file with .rpmsave suffix, but once package was removed these files are outside of RPM management and need to be removed manually.
If file is not listed as part of package, nether RPM (zypper) nor DPKG (apt) will touch it, unless package includes scripts to explicitly clean up such files.
I use “sudo rpmconf -a” (from rpmconf package) to remove such leftovers, I believe this is what OP is looking for. It’s an interactive tool, also helps to deal with configuration conflicts from package updates.
Wow, thanks a lot. This is what I was looking for. Thanks.
Note to all users. I didn’t want to compare zypper and apt. I just wanted to know how to remove/clear user configurationfiles of any package like what “apt purge” does, but on openSUSE, not to remove unused packages which would belong to “apt autoremove”.
Well, as many here I do not know what those apt commands are supposed to do (and no, we, at least I, are not going to study apt documentation for this lone case), thus saying things like “I want some thing that works like apt-xxx” will not help much. You must define/describe what exactly the effect should be and then we may hope that people here will offer you some (combination of) command(s) that do what you describe.
That said, are you sure that your apt command will visit the home directories of all users on a system and remove there files it assumes to belong to a certain software package?
As user, I would be very upset if my system manager would execute things like that and meddle with data I have in my own space, my home directory. >:(
I do not know exactly what the rpm command advised by @awerlang does, but what he describes seems to come very near to what you want. But I doubt it will change things in users’ home directories. It will probably at the most handle system configuration files.
For details of a recommended way of removal see this example “How to cleanly remove a package from a Debian-based distribution” by Jack Wallen: “When you uninstall an application from Linux, make sure you’re doing it in such a way as to remove both configuration files and dependencies.” What are those two commands? Let me demonstrate
Cleanly removing packages with zypper generally requires running both “zypper remove --clean-deps PACKAGE” and “zypper packages --unneeded | grep ^i|cut -d ‘|’ -f3|xargs zypper rm --clean-deps”.*
I didn’t want you or anyone here to study apt commands. That’s why in my thread’s title, I described my question pretty clear regarding the removal of user configuration files of “zypper remove” that I wanted to know. If zypper does that, then yes, if not, then thanks for the other tools that anyone here recommended to be used in place of “apt purge”.
AFAIK, there’s no package manager that would delete user configuration files in home directory. Even “apt purge” doesn’t do that. rpmconf doesn’t do that also.
Now I know that “zypper remove” doesn’t remove user configuration files like “apt purge”, and I have to use rpmconf for that. Thanks.
Those are NOT user configuration files. They are system configuration files. And yes, system configuration files of a program (often in /etc) are valid system wide to the program and thus are valid for all users that use the program (if it is a program to be used by users), but they are still not user configuration files to be manager by the user.
It seems that you use “user configuration files” in a different way then most people do. I wonder what in your opion are then “system configuration files”.