

My arch install is 10 years old at this point.
I would be interested to know what inspired the need to “feel fresh” from OP. Is this an extremely underpowered laptop that just can’t handle having a few extra packages installed? Is it the Windows bad habit just making them perceive it as “needing a cleanup” ?
If you have hard drive space, unloaded packages are generally never loaded and just take up storage, not CPU/memory (though you should check to see what services are running too).
Also importantly. pacman -Qdtq
and pacman -Rns
are 2 separate commands.
“Qdtq” means “Query, dependencies, unrequired, quiet” (“quiet” makes it so just the package names are output, to be more neatly piped into the second command. This queries the unrequired dependencies (ie, packages that were installed along with another package, but are no longer used by another package), and lists them
“Rns” means “Remove, no backup, recursively” . and the -
at the end means “Use the values from the first half of the pipe”… This removes the packages listed, skips creating any .pacsave
fields for config files, and then once the package is removed, checks all of ITS dependencies to see if they can be removed as well.
For this command, a “dependency” is any package that is installed as a dependency of another package (and hasn’t been directly installed manually). If you installed package X, and it brought in package Y and package Z, then uninstalled package X, and now youre worried about package Y and Z, this will find them and clear them out.
This also teaches us that if you uninstalled package X with pacman -Rs packageX
, the s
bit would make sure that package Y and Z were cleaned up at removal time in the first place.
But overall, there’s very little reason to reinstall arch unless you are running out of disk space due to how many obsolete packages you have hanging around and they are all explicitly installed so wont be cleaned up with the above method.
But worst case, if you manage to break things just by clearing out unused dependencies, you can just copy your files off and do a full reinstall. Your system works right now, why reinstall? Might as well try to improve it a little bit (if thats even needed) before giving up and starting over.
According to Debian users, “stable” means “unchanging” and not “doesn’t crash or have bugs” … If you still ship 100% of the changes but just delay them by 2 weeks, you have the same number of changes. So by the Debian definition of “stable”, no, it is the exact same as arch.
By the everyone else definition where “stable” means “doesn’t crash or have bugs”, then also no. Shipping buggy code 2 weeks later doesn’t reduce bugs. And if you use the AUR at all, then things get worse, I’ve found, as the AUR pkgbuilds expect dependencies to match current up to date Arch repos.
tl;dr - no