[maemo-developers] Re: QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)
From: Mikko Vartiainen mvartiainen at gmail.comDate: Tue Dec 1 17:32:14 EET 2009
- Previous message: QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)
- Next message: QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > I still suggest meta user/* packages. Nokia is actually using meta > user/* packages (for example, "Maemo 5" package is a meta package > pulling the platform non user/* packages when upgraded). Meta packages are unfortunately the only working way get library updates to users. I still would hate to see all libraries in Application Manager, even if they were semi hidden to some category. Only _good_ solution that I can see is that Application Manager would work the same way as apt-get and upgrade all packages (except the Nokia meta package). -- Mikko Vartiainen
- Previous message: QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)
- Next message: QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]