[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: Benoît HERVIER]

What happen if i push something for testing like PyGTKEditor for example ...
but once this one has been push, a new version of a python binding used by
PyGTKEditor exist in the extras-devel, we cannot push it to extras-testing
manually  ? But as there isn't any new version of PyGTKEditor, i ll recreate
one package in extras-devel with a greater number just to push the python
binding.

What happen now if this binding is a important update ?

2009/12/1 Mikko Vartiainen <mvartiainen at gmail.com>

> 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.
> From Nokia's perspective it's probably not broken because they can
> control that single meta package for SSU. How could we get that fixed?
>
> ---
> Mikko Vartiainen
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>



-- 
Benoît HERVIER - http://khertan.net/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20091202/83df118a/attachment.htm