> 1. building appstores or repositories that can be used by different Linux > distributions, comforming to different > levels of LSB, and then populated by different apps devellopers, hopefully > including big packages like gnome and > kde, and possibly also packagers picking up sources, maybe even debian > packagers. > In this way even smaller distros could have a large set of packages, and > developpers could have one place > to address a lot of distros.
Already works today with flatpak. Gnome, KDE and the like own and control their own ABI policies. > This could be built for the different architectures including i386, amd64 > and arm. i386 is dead anyway except for legacy support. > 2. security updates > iot devices, mobile telephones, tv-sets etc have severe problems with > security updates and general updating. > LSB could pobably be helping out with this, especially for smaller firms, > that have not gotten their own systems. And this really has nothing to do with ABI problems and everything to do with competence and legal incentives. IOT you usually control the full stack so the ABI is really irrelevant, you can roll your new build without even caring about the ABI of the previous one. The Android train-wreck isn't at all LSB relevant because they don't even use the same libraries, and the user space ABIs are totally unrelated to LSB anyway. Alan _______________________________________________ lsb-discuss mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/lsb-discuss
