2 ms·

Thing is that he is blaming distros for the situation, when distros are trying their level best to make things usable while upstream keeps changing the "rules".

• icedchai 9y ago
  He should be blaming their distros. It's their policies causing these problems, not a true technical issue. They should include those (modified) libraries as part of his app's package, where only his app uses them. This is actually the simplest way to package anything: include all the dependencies, isolated from the rest of the system. He's right, Mac and Windows figured this out ages ago.
  • lobster_johnson 9y ago
    Indeed, while macOS has global libraries ("frameworks") such as Cocoa, Core Data and so on, which are obviously versioned along with the OS (with a semver type system to handle compatibility issues), user libraries are typically bundled together with the app. While macOS comes with shared libraries in /usr/lib such as like readline, LibXML and OpenSSL, trying to use them from an app is almost always a bad idea, most of all because the libraries tend to be very old. Many Homebrew packages have an install flag to control whether they should link to the system libraries or provide their own.