

Unfortunately, this doesn’t tell us which specific packages were installed, nor does it give us the commands used or options used in conjunction with the comma nds. The Number of files and/or packages altered.We get an output similar to this: No Commands are Shown If we use the history feature built into YUM by typing the following: yum history But how do we know which packages we installed manually? It’s a good practice to clean them out every now and then. This results in packages accumulating over a period of time, using up space, and cluttering our system files. We can often install stuff that only ends up getting used a handful of times, which then ends up getting forgotten about being installed in the first place. Getting a List of Manually Installed Packages So if you’ve been installing stuff, upgrading older packages, or updating CentOS itself, YUM will keep a record of it all. The idea of that command is to give you a general idea of what package operations you’ve carried out recently.


Take YUM’s “history” command, for instance. Sure, it’s better than using the even more barebones RPM package manager, but it still leaves a lot to be desired. Sometimes, working with YUM – the default CentOS package manager – can feel unintuitive and cumbersome.
