not sure, maybe the strict dep can be dropped as last time it was due
broken openssl build breaking sslv2 symbols.
but i'd rather keep it strict dep, as it has been broken several times
in the past if openssl was upgraded because rpm doesn't support forward
library dependencies. i.e if python was compiled with openssl 1.0.0
being installed at compile time then having the same old python
installed but openssl upgraded to 1.1.1 installed will still work, but
not opposite way. or something like such scenario. somebody suggested to
add version map to openssl like debian does, but that was just left as
the discussion, nothing actually implemented. the threads are several
years old so it takes time to find those.
On 03.05.2016 23:59, Arkadiusz Miśkiewicz wrote:
What's the rebuild procedure in case of openssl bump after this change?
commit 9a0fad23f3d83106291fc38815d3fa40a2063ee7
Author: Elan Ruusamäe <[email protected]>
Date: Fri Mar 4 10:10:31 2016 +0200
openssl 1.0.2g rebuild, strict openssl version dep
See recent openssh/python/python3 build logs.
--
glen
_______________________________________________
pld-devel-en mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
