On Sunday 25 February 2001 23:26, Lenz Grimmer wrote:
On Sun, Feb 25, amircea@libertysurf.fr wrote:
Unfortunately RPM is not very well documented. RPM has to methods of determining package dependencies. During the build process of a package, it uses "ldd" on all binaries to determine all required shared libraries. It can also automatically detect dependencenies on required script languages like Perl or bash. In addtion to that, a package maintainer can add additional dependencies on certain packages by adding them to the "Requires:" field of the spec file. If you want to find out, what a package requires, you can run "rpm -qRp
" The problem is: if you installed certain libraries by hand (without using RPM), it cannot determine, that these libs are actually installed and will complain about missing dependencies. The only way to work around this is to use the "--nodeps" flag or build your own RPMs for these libs.
Bye, LenZ
Lenz, Can't we also use the politician's approach and lie? In other words rpm --justdb ( - update the database, but do not modify the filesystem.) rpm is difficult to figure out, but I've had reasonable success playing with the commands and keeping a copy of rpm --help > rpm-help.txt wrapped up in an applnk to kless. Steve