The common RPM friends know that RPM is easy to use, but its dependencies are the most headache! Sometimes, for example, a packet needs a B bag, B packet needs C package, C package needs a package, OK. This is the most common deadlock (like a database with wood?). )。 This time there are several ways to solve the problem:
A, forced installation----violent type
Use Rpm-i--force--nodeps to force the installation. Ignore dependencies. This way you can first pack a package, then pack B, and then pack C. This is still a bit of a hidden danger, the feeling is not very practical (although in fact, not found what is not good). The prerequisite for success after installation is that you need to be clear about dependencies and pack all of them. The advantage is that they do not have to control their specific dependency sequencing.
B, disposable full-load---clean sweep type
Can be dependent on a few of the packages out in the same folder and then Rpm-ivn *.rpm This can also be a prerequisite is not less.
C. Install using Yum technology--Using server mode
Yum is a server resource technology. How to download server resources online. Cons: Too cumbersome. To set up a bunch of things. Pros: After setting up, it is convenient and most of the resources you need can be found on the server. It feels like maven2.
Reference: http://wenku.baidu.com/view/428c851352d380eb62946ded.html
D. Install the dependency library using the solution provided by Redhat (highly recommended)
Example: Install rpmdbFirst, then use
# RPM-IVH--aid samba*.rpm (be sure to install Rpmdb before you can install exclude dependencies in this way)
This command automatically installs the packages that need to be installed in the dependency relationship, including:
cups-libs-1.1.17-13.3.6.rpm
samba-common-3.0.0-14.3e.i386.rpm
samba-3.0.0-14.3e.i386.rpm
samba-client-3.0.0-14.3e.i386.rpm
can be easily solved by directly installing samba-3.0.0-14.3e.i386.rpm or samba-client-3.0.0-14.3e.i386.rpm on samba-common-3.0.0-14.3e.i386.rpm , while the installation of sambacommon-3.0.0-14.3e.i386.rpm appears dependent on the Libcups.so.2 library file, and the RPM package where the library file resides cannot be determined quickly
These methods can quickly resolve dependencies
This article from "Tangjilinux" blog, declined reprint!
Several methods for solving RPM packet dependencies