Ah hah.
The procedure is:
1. rpm -ql --whatprovides | grep libcrypto.so.1 etc.
2. If #1 is TRUE, then fixed /etc/ld.so.conf
If you think about it, #2 will never ever be done if #1 procedure is not TRUE. This is not a 'must be done' but sys-admin 'good practice' policy.
In other words, the procedure does NOT say '/etc/ld.so.conf' is being examined by 'rpm' to find the library, as you think it does. Rather, it is 'rpm' itself that finds the dependency, that's why #1 procedure is there as first and foremost.
#2 procedure is there to always ensure that when the program is executed, the program library loader will always be provided with the 'correct' information to enable it to load the library. There are 'rpm' that are not well-behave in the sense that default library locations(/lib;/usr/lib;/usr/local/lib) are not always used for libraries, as 'rpm' relies on the packager's abilities to cover all alternatives and for it to behave accordingly.
The intelligence of 'rpm' depends on the packager. The 'rpm' can't read what one wants, so to speak. The packager has to expressly tell 'rpm' what's 'good practice'.
So, it is a matter of sys-admin 'good practice' to always confirm these things, so no one gets bug down chasing the 'rainbow', as you have been in that situation previously.
I hope this has clarified the mis-interpretations.
O Plameras wrote:
So, what is the mechanism for it to know if there is or not.
And if there is, how will the program loader find where to load the libraries required ?
James Gregory wrote:
Quoting Voytek <[EMAIL PROTECTED]>:
<quote who="O Plameras">
Edit your /etc/ld.so.conf and insert the the directory path
excluding the filename.
RPM doesn't inspect ld.so.conf in walking dependencies. This will have no effect
on the installation.
(hhhm, perhaps Eric was right telling me to give it up...?)
I'm inclined to agree that 7.3 is a little old to be expecting updates on.
Perhaps you can tell us about the system and we can help you get it upgraded?
What do you use this box for?
I'm curious though, why are you asking yum to install dependencies you've
manually specified and not asking it to install proftpd and fetch all of its
dependencies for you?
yum install proftpd
seems easier. What was the source of your proftpd rpm anyway?
At any rate, this package:
http://rpm.pbone.net/index.php3/stat/4/idpl/776260/com/openssl096-0.9.6-23.7.i386.rpm.html
claims to provide the files you're after. It might be a solution to your imediate problem.
I generally search on rpm.pbone.net for the filename when these dependency
questions come up. They have quite an extensive index.
HTH,
James.
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
