Cleaning up your arch packages is a bit of a chore. The key document listing the pacman invocations you will need is pacman/Tips and tricks (ArchWiki).
The basic flow I use is:
- list explicitly installed (
-Qe), - remove (
-R) any that I don't explicitly want, - remove orphans (
pacman -Rns $(pacman -Qtdq)).
I always end up with a bunch of KDE packages installed which I find annoying because it makes my upgrades go a lot slower due to their size and frequency of update. They must be pulled in by one of my explicit installs. Time to generate some dependency graphs:
- The PacVis homepage has a nice overview of package dependency visualization tools.
- pactree is in the pacman-contrib package (this took me about 20 minutes to figure out; there is a "tip" at the top of [Pacman (ArchWiki)[https:/
/ wiki.archlinux.org/ index.php/ Pacman]). - gephi is a powerful graph explorer. Need to find a meaty graph problem to use to learn it. This is probably not meaty enough.
Pactree reveals that krita is pulling in all those KDE packages. Well, I want to keep krita so I guess I'll put up with them :D.
With the option of this feature I am also using the version of this operating system and it has been pretty useful for professional working. There are many operators that are using same version of linix.
writemypaper4me.org, Jun 24 2018 on edrex.pdxhub.org