https://bugzilla.rpmfusion.org/show_bug.cgi?id=2565
--- Comment #5 from Jonathan Dieter <jdieter(a)gmail.com> 2012-11-08 19:07:14 CET ---
(In reply to comment #3)
At a second thought, I think "my" way is correct for two
reasons:
- Practically, at last release upstream apologized for still using 0.9.8 i. e.,
they will shift to 1.0.0 quite soon.
- The links used all points to an object with the same soname as the original.
However, the libssl 0.9.8 has not the same soname as 1.0.0, same applies to
libssl.
Together with the stability problems (above) I think this boils down to
keeping the bundled libssl/libcrypto until upstream upgrades to 1.0.0 - which
probably isn't that long.
Agreed. There are generally good reasons for soname changes, so, while a
symlink might work for a while, there's no guarantee that the application won't
call some function that has changed and segfault.
--
Configure bugmail:
https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.