3 ms·
If you have some basic library that would be updated by your distribution, you have pretty much big chance that it would be part of the runtime and updated by r
by danieldk 6y ago
If you have some basic library that would be updated by your distribution, you have pretty much big chance that it would be part of the runtime and updated by runtime maintainers, not by the application authors.
Unfortunately, this is not true. Many of the Flathub Flatpaks compile custom versions of a lot widely-used libraries. E.g., the most recently updated Flathub package of an open source project (as of writing), compiles by itself [1]:
Boost 1.73, Eigen 3.3.7, OpenCV 4.3.0, exiv2 0.27.2, marble 20.04.1, lensfun 0.3.2, ImageMagick 7.0.10-13, libgphoto2 2.5.25, libusb 1.0.23, jasper 2.0.16, libksane 20.04.1, sane-backends 1.0.27, libqlr master, qtav 1.13.0, x265 3.3
Most of these are standard dependencies that are in most Linux distributions.
[1] https://github.com/flathub/org.kde.digikam/blob/2d0b5b369382afa08074bc72b34774c022fe15ef/org.kde.digikam.json https://github.com/flathub/org.kde.digikam/blob/2d0b5b369382...
- vetinari 6y agoWidely used does not mean, that they are good candidate for a platform library. Many of them do not have stable API, so you either keep everything on an ancient version (hopefully compilable against), or stuff breaks. E.g. Boost. Fedora 32, which was released this April, but has version 1.69 (released in Dec 2018), while the current one is 1.73. Similarly, ImageMagick is updated every few days. In these cases, it is better to let the applications decide which versions they want, and keep up with updates.