In Conclusion

You'll have to manually resolve rpm dependency failures when you install packages that are not a part of your distribution. However, once you know the name of the shared library package that was used to create the shared object, or soname, reported in the rpm dependency failure error message, you may be able to use an automated tool to download and install it.

The trick is that the soname reported in the dependency failure error message by rpm is normally not related to the shared library package name (and thus the shared library rpm package name) that was used to create it.