Re:Oasis: Small statically-linked Linux system
by rattlesnakedave on Sunday August 14, 2022 @10:35AM
(#32459588)
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.
[ Parent
| on HN ]
Re:Oasis: Small statically-linked Linux system
by itvision on Sunday August 14, 2022 @11:11AM
(#32459908)
Haven't seen a single OpenSSL issue over the past 25 years of using Linux.
libstdc++ errors? Seen them.
Re:Oasis: Small statically-linked Linux system
by pfarrell on Sunday August 14, 2022 @11:34AM
(#32460092)
Libstdc++ errors notwithstanding, what about heartbleed?
Re:Oasis: Small statically-linked Linux system
by RealStickman_ on Sunday August 14, 2022 @12:31PM
(#32460564)
I think the parent was talking about dependency conflicts, not issues in OpenSSL.
Re:Oasis: Small statically-linked Linux system
by nicce on Sunday August 14, 2022 @10:46AM
(#32459685)
It 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.
Re:Oasis: Small statically-linked Linux system
by convolvatron on Sunday August 14, 2022 @01:17PM
(#32460994)
How 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
Re:Oasis: Small statically-linked Linux system
by arinlen on Sunday August 14, 2022 @03:08PM
(#32461967)
> 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.