[maemo-developers] QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)
From: Anderson Lizardo anderson.lizardo at openbossa.orgDate: Tue Dec 1 17:39:04 EET 2009
- Previous message: Re: 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 ]
On Tue, Dec 1, 2009 at 11:32 AM, Mikko Vartiainen <mvartiainen at gmail.com> wrote: >> >> 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). The problem being that the meta-package will pull *all* PyMaemo packages and not just what the user wants/needs :/ Unless Application Manager honours Suggests: fields ? in this case we could put all non-core Python packages under that field. The other solution is to fix Application Manager :o) Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil
- Previous message: Re: 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 ]