3 ms·
Google “OpenSSL dependency conflict” and view the results. There is significantly more work going on when OpenSSL releases and update than “just update the sing
by rattlesnakedave 4y ago
Google “OpenSSL dependency conflict” and view the results. There is significantly more work going on when OpenSSL releases and update than “just update the single shared library file.” Applications often need to be updated as well, so you may as well just statically link the new binary.
- nicce 4y agoIt really depends on whether the bug is in API or not. If it is not, it is likely that upgrading only the shared library is enough.
- convolvatron 4y agoHow lovely to live in a world where api contracts are absolute and complicated internal behaviors never conflict in unforeseen ways. We’ve really gotten on top of the software complexity problem
- hedora 4y agoThat's exactly the problem deb files and apt solve (via integration testing and documenting antidependences.)
- arinlen 4y ago> How lovely to live in a world where api contracts are absolute and complicated internal behaviors never conflict in unforeseen ways. Some libraries managed to preserve API contracts throughout the years just fine. Even in C++, a language which does not establish a standard ABI, has frameworks which have not been breaking the ABI throughout multiple releases, such as Qt.
- itvision 4y agoHaven't seen a single OpenSSL issue over the past 25 years of using Linux. libstdc++ errors? Seen them.
- pfarrell 4y agoLibstdc++ errors notwithstanding, what about heartbleed? https://en.m.wikipedia.org/wiki/Heartbleed https://en.m.wikipedia.org/wiki/Heartbleed
- RealStickman_ 4y agoI think the parent was talking about dependency conflicts, not issues in OpenSSL.