On Mon, Feb 26, 2001 at 09:01:12AM +0100, amircea@libertysurf.fr wrote:
Thank you, Lenz. Let me reformulate my question though. What system database is rpm looking at, to decide whether a library exists in the system? Where is this database ?
/var/lib/rpm/* I doubt you can change anything there. You may read more at http://www.rpm.org -Kastus
I refer of course to the installing phase, not to the building phase.
On Mon, Feb 26, 2001 at 05:26:10AM +0100, Lenz Grimmer wrote:
On Sun, Feb 25, amircea@libertysurf.fr wrote:
On my systems I use to have programs installed both from rpms (from SuSE distros or other) and by compilation from source. I also mix distributions, e.g. 6.3, 6.4, 7.0 and even 5.1 or 5.3 coexist more or less peacefully on my hard disks. Being such an indisciplined user implies that I have a recurrent problem: many times when I want to install a rpm package, it complains about the missing of such and such library. Often the library is there and is active and if I install the package using the --nodeps option it works well. So, I would very much like to know more about the mechanism used by the rpm program to find out if the dependencies are present on the system. From the 'man rpm' I could not find this information. How can I find it ? Thanks for your help.
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 Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany While eating an elephant advance one bite at a time.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq