4 ms·

Ok maybe this is dumb question and is addressed somewhere: If a security problem is found, e.g. in muscl (the C lib), then is the user supposed to rebuild every

• qz2 6y ago
  Yep. And also because it's statically linked and optimised, which version of musl that ships in that binary may be obfuscated somewhat. And no, I don't get it either.
• rini17 6y ago
  Not a dumb question just there is always a catch: dynamical link saves you from rebuild only if the fix is carefully backported (by a distributor), which can introduce issues, too. The upstream has usually moved on in the meantime and the library isn't binary compatible.
• mforney 6y ago
  Yes, but with the oasis build system this is just a single command to do an incremental build that relinks your binaries and takes a matter of seconds. The user experience is essentially the same as updating your system on a dynamically-linked system. There is no "partial build" where some binaries get relinked but not others.
• eeZah7Ux 6y ago
  Yes, and this is why Linux distribution exist. Good luck maintaining 100.000 statically linked libraries embedded in 10.000 applications.
  • anthk 6y ago
    That's the point, you need less than 100. A browser, cloc, sbase, ubase, X/Arcan, mpv, youtube-dl, ffmpeg, mocp, lynx/link, bitlbee, irssi and not much more. On games, mednafen can emulate well a huge stack of systems, slashem/nethack is highly replayable and chocolate-doom has tons of PWADs (maps, levels and total conversions). Not the most modern gaming, but these are options to almost never be bored. For everything else you can spawn an x86 vm with tinyemu and forget maintenance.