The only reason why you would ever want to use RPATH with OpenSSL is
because you need to install a particular old version of libssl (or
libcrypto) that has the same SONAME as the system-default, but where you
don't want to use that system-default one -- but why would you want to
do that? Security updates are a good thing, usually.
On 5/30/17 8:58 AM, Jakob Bohm wrote:
> On 29/05/2017 16:39, Wouter Verhelst wrote:
>> ...
>> The only reason why you would ever want to use RPATH with OpenSSL is
...
Well, 'different strokes' to be sure ...
but, here, especially with lots of apps still not at all v110
compatible, or at best broken in their attempts, having local builds of
both v110x and v102x is extremely useful -- and RPATH'ing makes that
trivially manageable.
My $.02.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users