3 ms·
The solution for this is quite simple: split the distro to a core, and a separate 'apps' repository, and let app authors control (but with a mandatory QA step)
by bergie 15y ago
The solution for this is quite simple: split the distro to a core, and a separate 'apps' repository, and let app authors control (but with a mandatory QA step) when their software gets released or updated. We did this with Maemo (and later MeeGo), and it has worked great:
http://bergie.iki.fi/blog/application_quality_assurance_in_linux_distributions/ http://bergie.iki.fi/blog/application_quality_assurance_in_l...
Cross-distro app repositories are also a possibility, thanks to the Open Build Service (http://openbuildservice.org http://openbuildservice.org). And since MeeGo's community apps service is open source (https://github.com/nemein/com_meego_packages https://github.com/nemein/com_meego_packages), all software needed for this (including an app store client app) already exists.
What is needed is a major distribution to make the first move on this.
- DrCatbox 15y agoYou would still need to maintain and manage the core distro. The packages in their would update and break the systme, you'd have lvm issues and what not. Any way, care to give links to more on maeom/meegos architecture?
- bergie 15y agoYou still package and build an application separately for each distro version. And then the community tests it before it goes to the stable apps repo. So broken packages (either by packaging, or by app not functioning properly) are unlikely to pass QA. So if your package conflicts with something, either fix that issue or don't release for that distro versio.
- joe_the_user 15y agoOff-topic: Is active Meego Development still happening? I'm a QT developer and might be interested in contributing a little...
- bergie 15y agoThe MeeGo community effort continues at http://merproject.org http://merproject.org Used already as the base distro in the Spark tablet