[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: Henrik Hedberg]

Anderson Lizardo wrote:

> Some user suggested once creating meta user/* packages for libraries,
> python modules etc. that need updates, but I think this just too
> hackish, and even if we proceed and do this, how do we convince the
> end user to install it?

    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).

    However, there might still be a question about how to convince an 
end user to upgrade a package that he has not actually installed. In 
"Maemo 5" case that is easy, but in other cases it might require some 
additional communication.

    One solution could be that the Application Manager showed other 
user/* packages that depends on meta user/* packages. That way an user 
might understand that if he upgraded Python package (or Microfeed 
package), gPodder (Mauku), for example, would benefit from that. Maybe 
those meta packages should be in a separate section (user/backend, 
user/platform, user/libraries, or similar).

    BR,

    Henrik

-- 
    Henrik Hedberg  -  http://www.henrikhedberg.net/