Библиотека сайта rus-linux.net
|Maximum RPM: Taking the Red Hat Package Manager to the Limit|
|Prev||Chapter 3. Using RPM to Erase Packages||Next|
ejectpackage was erased. There isn't much in the way of feedback, is there? Could we get more if we add -v?
Still nothing. However, there's another option that can be counted on to give a wealth of information. Let's give it a try:
First, RPM displays the package's record number. The number is normally of use only to people that work on RPM's database code.
Next, RPM executes a "pre-uninstall" script, if one exists. This script can execute any commands required to remove the package before any files are actually deleted.
files test = 0" line indicates
that RPM is to actually erase the package. If the number had been
non-zero, RPM would only be performing a test of the package erasure.
This happens when the --test option is used. Refer
to the section called --test — Go Through the Process of Erasing
the Package, But Do Not Erase It for more information on
the use of the --test option with rpm
The next two lines log the actual removal of the files comprising the package. Packages with many files can result in a lot of output when using -vv!
Next, RPM executes a "post-uninstall" script, if one exists. Like the pre-uninstall script, this script is used to perform any processing required to cleanly erase the package. Unlike the pre-uninstall script, however, the post-uninstall script runs after all the package's files have been removed.
Finally, the last five lines show the process RPM uses to remove every trace of the package from its database. From the messages, we can see that the database contains some per-package data, followed by information on every file installed by the package.