The
# rpm -ivh --force --relocate
Preparing... ########################################### [100%]
1:httpd ########################################### [100%]
The change is recorded in the RPM database, so querying the database will show the actual, installed paths:
# rpm -ql httpd
/etc/httpd
/etc/httpd/conf
/etc/httpd/conf.d
/etc/httpd/conf.d/README
/etc/httpd/conf.d/welcome.conf
...(Many lines snipped)...
/usr/share/html/icons/world1.png
/usr/share/html/icons/world2.gif
/usr/share/html/icons/world2.png
Relocating files does not change configuration files, scripts, or programs that expect files to be located in particular locations. In the
The options for erasing software are a subset of the options for installing and upgrading; the most useful options are listed in Table 5-4 .
Table 5-4. rpm package-removal (erase) options
Option | Description |
---|---|
--allmatches | Erases all packages matching the name given (useful if more than one version is installed). |
--nodeps | Proceeds with the package removal even if doing so will break some dependencies for other packages. |
--noscripts | Prevents removal scripts in the package from running. |
--notriggers | Prevents trigger scripts in other packages from running. |
--repackage | Repackages the files being removed so that the removal can be undone (rolled back). See Lab 5.4, 'Rolling Back a Package Installation, Upgrade, or Removal.' |
--test | Checks for conflicts and potential problems, but does not make any actual changes to the system. |
5.2.2. How Does It Work?
RPMs are named using the pattern:
in which:
The name of the software in the package.
The software's version number.
The package version number; if one version of the software has been packaged a few times (for example, with different file locations, scripts, triggers, or sample data), this number is incremented while the software version number is left unchanged.
The architecture for which the package is compiled (
1. The viability of the operation requested is analyzed.