If they are indeed the same package, just create a soft link to your
currently installed lib but name it with the other naming standard ala:
cd /lib
ln -s ./libcrypto.so.0.9.7 ./libcrypto.so.4
Regards, Marshall
Message
From: redhat-list-bounces (AT) redhat (DOT) com
[mailto:redhat-list-bounces (AT) redhat (DOT) com] Behalf Chris St. Pierre
Sent: Thursday, June 29, 2006 1:04 PM
To: redhat-list (AT) redhat (DOT) com
Subject: libcrypto names
I've got an RPM that requires libcrypto.so.0.9.7. The problem is that
RHEL's SSL package provides libcrypto.so.4. Some googling
suggests that these are, in fact, the same library, just named
differently: the .4 is an RHEL thing, while the .0.9.7 is the SSL
version. (The RPM is packaged without a specific distro in mind.)
How can I solve this dependency, preferably without installing a
non-RHEL SSL package?
The only thing I can think of is to create an RPM package that just
installs a symlink to libcrypto.so.4 under libcrypto.so.0.9.7, and
reports to the RPM database that this package provides
libcrypto.so.0.9.7. This seems like overkill, and I'm also a total
noob when it comes to making my own RPMs. ideas?
Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University

While that would functionally work, my RPM install would still fail --
unless I use , I suppose. That's ugly, though, as we don't
have written into any of our scripts, crontabs, Cfengine
rules, etc., and don't want to. I'm looking for a way to do this
"politely," I guess.

Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University

Thu, 29 Jun 2006, McDougall, Marshall (FSH) wrote:

>If they are indeed the same package, just create a soft link to your
>currently installed lib but name it with the other naming standard ala:
>
cd /lib
ln -s ./libcrypto.so.0.9.7 ./libcrypto.so.4
>
>Regards, Marshall
>
Message
>From: redhat-list-bounces (AT) redhat (DOT) com
>[mailto:redhat-list-bounces (AT) redhat (DOT) com] Behalf Chris St. Pierre
>Sent: Thursday, June 29, 2006 1:04 PM
>To: redhat-list (AT) redhat (DOT) com
>Subject: libcrypto names
>
>I've got an RPM that requires libcrypto.so.0.9.7. The problem is that
>RHEL's SSL package provides libcrypto.so.4. Some googling
>suggests that these are, in fact, the same library, just named
>differently: the .4 is an RHEL thing, while the .0.9.7 is the SSL
>version. (The RPM is packaged without a specific distro in mind.)
>How can I solve this dependency, preferably without installing a
>non-RHEL SSL package?
>
>The only thing I can think of is to create an RPM package that just
>installs a symlink to libcrypto.so.4 under libcrypto.so.0.9.7, and
>reports to the RPM database that this package provides
>libcrypto.so.0.9.7. This seems like overkill, and I'm also a total
>noob when it comes to making my own RPMs. ideas?
>
>Chris St. Pierre
>Unix Systems Administrator
>Nebraska Wesleyan University
>

>redhat-list mailing list
>unsubscribe mailto:redhat-list-request (AT) redhat (DOT) com?subject=unsubscribe
>
>

>redhat-list mailing list
>unsubscribe mailto:redhat-list-request (AT) redhat (DOT) com?subject=unsubscribe
>
>