When you install a package, it keeps track of all the files so when you uninstall it, it removes them all. There’s various ways to scan and remove untracked files, but on a Linux system you can basically be ask it “where does this file comes from?” and it’ll just tell you “oh, that’s from mpg123, and you have it installed because VLC and Firefox need it to decode some AVIs”. And if you really don’t want it for some reason, it can also go uninstall everything that needs it too.
It makes it pretty hard to corrupt a system or uninstall important stuff. In the reverse, it also knows what is needed, so if you install VLC, it will also install all the codecs with it, and those are also automatically available to other apps too usually.
While that is true for the files that make up the programs themselves and their dependencies, it’s not true for any state files or caches that programs creates at runtime. You need to clean those up manually.
Central package management.
When you install a package, it keeps track of all the files so when you uninstall it, it removes them all. There’s various ways to scan and remove untracked files, but on a Linux system you can basically be ask it “where does this file comes from?” and it’ll just tell you “oh, that’s from mpg123, and you have it installed because VLC and Firefox need it to decode some AVIs”. And if you really don’t want it for some reason, it can also go uninstall everything that needs it too.
It makes it pretty hard to corrupt a system or uninstall important stuff. In the reverse, it also knows what is needed, so if you install VLC, it will also install all the codecs with it, and those are also automatically available to other apps too usually.
While that is true for the files that make up the programs themselves and their dependencies, it’s not true for any state files or caches that programs creates at runtime. You need to clean those up manually.
lmao, do a
ls -aR ~Thanks for the explanation!