3 ms·
And who packages glibc? Or udev? Or zlib (which is so quirky that it almost doesn't build at all out of the upstream source). That's where the packaging band
by ajross 15y ago
And who packages glibc? Or udev? Or zlib (which is so quirky that it almost doesn't build at all out of the upstream source). That's where the packaging bandwidth is spent in the distributions: middleware. Certainly not "apps", which are generally trivial to build as long as you have the dependencies correct. Take a look at, for example, the Fedora spec files for the software you use vs. the middleware and see the difference in complexity.
And note that Android's (which I assume is what you're referring to when you talk about "app bundles") middleware packaging is no less complicated (honestly it's a lot more so in a lot of ways -- no firm dependency tracking, everything must build all at once). Check the AOSP "external" tree.
- Aqueous 15y agoI'd expect that like other OSes core dependencies would still be managed by the distributor. But these are nothing but the barest essentials to making the OS work. I count udev, and glibc, and zlib among these. Mac OS X does this. But these are very few in number compared to the number of total packages that are stored on, for example, Ubuntu's repositories. If the price of having apps that just download and work on any distribution is having a more complicated middleware system, then I'll take it.