A good practice is to always keep your system up-to-date, this for security & stability. This is the number #1 advice to avoid problems.User1 wrote: ↑Fri Apr 13, 2018 11:15 amI did that but I guess we misunderstand each other maybe.
I'm talking about the general "good practice" how to try out some software and safely removing it afterwards in the case I don't want to keep it. Why is it that in my case the pulseaudio had only a few dependencies when installing and way more when uninstalling resulting in destroying my system?
That in mind, how secure is it to install the announced updates on a daily check? I don't want to have that kind of problems again only by keeping my system up to date.
Personally I use a virtual machine to build, install, test and uninstall packages. This way all the rubbishes left behind (settings I my have changed, configurations files in the home directory, log files, ...) remain in the VM and my system stays clean. It could be an option for you if you want to experiment things.
The best way to test an applications and then remove them assuming you don't install anything in between is to the "tackeback" option of "eopkg history". This allows you to rollback to a specific operation number (all operations following the given number will be undone).
So Imagine you just installed "application xyz" to test it and you want to remove it, type "eopkg hs" to find the operation number, you'll see something like
Operation is 440, so you want to rollback to the preceding operation -> "sudo eopkg hs -t339"Operation #440: install
Date: 2010-01-01 01:01
* application xyz 1.2-3-1-x86_64 is installed.