[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: Mikko Vartiainen mvartiainen at gmail.comDate: Tue Dec 1 17:55:35 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 ]
On Tue, Dec 1, 2009 at 5:39 PM, Anderson Lizardo <anderson.lizardo at openbossa.org> wrote: > The problem being that the meta-package will pull *all* PyMaemo > packages and not just what the user wants/needs :/ Yes, meta packages would bring more problems than solve them. > Unless Application Manager honours Suggests: fields ? in this case we > could put all non-core Python packages under that field. I don't think HAM knows about suggests field. > The other solution is to fix Application Manager :o) IMO Application Manager is broken from community (Extras) perspective.
- 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 ]