If #xz were a Go or Rust dependency, you wouldnโt have a single copy of xz library on your system, but many, #xzbackdoor hidden in every executable that uses it. Distros would have to rebuild all packages using that lib (not just the lib itself), which could take days or weeks, and users would have to update them all, downloading tens or hundreds of megabytes.
If you install binaries directly from vendors/devs, itโs even worse โ you wouldnโt even know which ones are affected and youโd (1/3)
Luca Sironi likes this.
reshared this
Jakub Jirutka ๐ช๐บ๐บ๐ฆ
in reply to Jakub Jirutka ๐ช๐บ๐บ๐ฆ • • •be at the mercy of the devs to provide the update. Not a group of active maintainers behind the distro, but many individual devs, some of whom lack the time or motivation and sustainability. The same goes for Docker containers, Flatpak and similar!
This is called static linking or bundling. Instead of rebuilding and updating a single shared library, you have to rebuild and update every single thing that links/bundles it. In the case of static linking, you usually canโt even tell which (2/3)
reshared this
Elena ``of Valhalla'' e coucouf โ reshared this.
Jakub Jirutka ๐ช๐บ๐บ๐ฆ
in reply to Jakub Jirutka ๐ช๐บ๐บ๐ฆ • • •libraries itโs linked with!
Now do you see the value of #Linux distros and dynamic linking? Please, stop this insane โsingle binaryโ mantra and work with distros, not against them.
If #rustlang wants to replace C, devs need to acknowledge this and start providing dynamically linkable libraries with stable ABI. (3/3)
reshared this
Elena ``of Valhalla'' e coucouf โ reshared this.
Jakub Jirutka ๐ช๐บ๐บ๐ฆ
in reply to Jakub Jirutka ๐ช๐บ๐บ๐ฆ • • •https://www.cvedetails.com/vulnerability-list/vendor_id-14185/product_id-29205/Golang-GO.html
Golang GO : Security vulnerabilities, CVEs
www.cvedetails.comAvebury Rosetta :transistor:
in reply to Jakub Jirutka ๐ช๐บ๐บ๐ฆ • • •federico
in reply to Avebury Rosetta :transistor: • • •you mean a huge blob? That's a docker image.
federico
in reply to Jakub Jirutka ๐ช๐บ๐บ๐ฆ • • •Aleksandra Fedorova :fedora:
Unknown parent • • •@ITwrx
Upstreams should not choose versions of dependencies randomly in their own bubble.
To make deduplication of effort work, there should be awareness in every upstream that they need to align their choices with other upstreams.
The packaging and distributions ecosystem is where different upstreams meet and talk to each other about things like which versions to choose as a base for LTS branches, which versions to choose for shared libraries and so on.
@kravietz @Conan_Kudo @jakub
Aleksandra Fedorova :fedora:
in reply to Aleksandra Fedorova :fedora: • • •@ITwrx
And I may be need a separate statement:
I don't believe that every upstream developer must become a packaging expert.
I believe that packaging is a job on its own. For some projects you combine roles of developer, tester, doc writer and packager, for some you just can't. And then you ask for help.
But I believe that upstream developer should be aware that there are needs in software development beyond writing the code and pleasing the user.
@kravietz @Conan_Kudo @jakub
Elena ``of Valhalla''
in reply to Aleksandra Fedorova :fedora: • •@Aleksandra Fedorova :fedora: @ITwrx @Neal Gompa (ใใผใซใปใดใณใ) :fedora: @kravietz ๐ฆ @Jakub Jirutka ๐ช๐บ๐บ๐ฆ and even for single person projects, having a packager in each main distribution that isn't the upstream developer is a big plus, as it provides a minimum of oversight and redundancy.
Not much, especially when said maintainer(s) are overworked and demoralized, but still better than nothing.
Aleksandra Fedorova :fedora:
in reply to Elena ``of Valhalla'' • • •@valhalla
Yes, that is an important point too.
When we say co-maintainer, we often implicitly assume that it should be an equally or comparably skilled person doing the same tasks.
And then we stop at a thought on how hard it is to find a duplicate.
While it doesn't have to be.
There is plenty of room for a developer to collaborate with a tester, or a packager or a build engineer, or a documentation writer.
It often can be healthier too.
@ITwrx @Conan_Kudo @kravietz @jakub
Elena ``of Valhalla'' likes this.