Poettering: Revisiting how we put together Linux systems

I think that some of the underlying problems with application bundles would go away if they were more widely used (by popular FLOSS projects I mean, not just by commercial ones). On the one hand people would gain more experience with creating them. A few examples:

* Experience of which libraries link well statically and which not. E.g. glibc vs uclibc.
* Experience of what ABIs one can depend on on a random system . E.g. the Linux kernel system call interface, the glibc dynamic interface (as long as one knows a few tricks).
* Avoiding statically linking to high-frequency update libraries. E.g. piping and shelling out to openssl(1) rather than linking in the library.

On the other hand I can also imagine popular hosting services adding build services which would improve the security problem. A developer who did not have the resources to follow all security updates could just let the service re-build and re-package the software whenever there was a security update to a bundled library, and they could use a standard (statically linked) library to check for and download updates at the hosting service on software start-up.