Hello, On 2024-04-08 13:43, Johannes Kastl wrote:
On 08.04.24 13:01 Neal Gompa wrote:
... %ghost entries ensure that data is cleaned up only on final uninstall. Leaving random crap all over the filesystem even after uninstall is a nightmare. You should use %ghost for known names of files that you do not create and either the admin or the software creates.
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.
All user's own data is sacrosanct. No automatism must remove user's own data. Removing user's own data requires explicit user confirmation. E.g. when a program has an interactive user confirmation dialog or when a program has a command line option which the user must deliberately specify, then it is OK when a program removes user's own data. Simply put: Only the user decides what happens with his own data. It is a different thing what programs currently do, in particular when something is done in a certain way since a very long time (in IT time scale), for example: ---------------------------------------------------------- $ echo "my data" >a $ echo "my other data" >b $ cp a b ---------------------------------------------------------- 'cp' overwrites "my other data" so this data is "removed". FWIW: This pattern is the only one how I unintendedly removed my own data in the past (I think two or three times). Kind Regards Johannes Meixner -- SUSE Software Solutions Germany GmbH Frankenstr. 146 - 90461 Nuernberg - Germany (HRB 36809, AG Nuernberg) GF: Ivo Totev