maemo.org > Community > Developer forum > QA Process for non user/* packages and how Application Manager handles upgrades (was: Re: extras-devel -> extras-testing auto-promotion not working?)
On Thu, Dec 3, 2009 at 3:42 PM, Anderson Lizardo
<anderson.lizardo@openbossa.org> wrote:
>
> * If I understood Mikko's explanation right, HAM will not upgrade a
> dependency automatically (unlike "apt-get upgrade"), unless a
> installed (or to be installed) user/* application exclicitely Depends
> on that new version (i.e. uses "Depends: package (>= x.y)", where x.y
> is the newer version). If that's correct, each new version of a
> dependency that contains a important fix will require *all* Python
> applications updating their versions to include the new required
> version in debian/control, if we want the user to have that fix.
>
> Mikko: feel free to correct me if I made a mistake.
Yes, you understood correctly.
> * installing this metapackage will obviously install *all* PyMaemo
> packages, which will take unnecessarily precious storage even if not
> all packages are used.
But this user/hidden (which I've never heard of) is different. It
seems that user/hidden packages get the same treatment as other user/
packages for updates, but they cannot be separately installed.
User/hidden pacakge could be part of the solution, but it's still
awkward and unnecessary hack compared to normal upgrades.
If user/hidden was used all python apps should depend on big pymaemo
metapackage, which would pull all packages even if not needed as you
said. But if user/hidden is already (or soon) there, it might be the
best option available. After all application space isn't big issue
anymore, and after installing 2-3 python application you have
practically installed all pymaemo packages anyway.
<anderson.lizardo@openbossa.org> wrote:
>
> * If I understood Mikko's explanation right, HAM will not upgrade a
> dependency automatically (unlike "apt-get upgrade"), unless a
> installed (or to be installed) user/* application exclicitely Depends
> on that new version (i.e. uses "Depends: package (>= x.y)", where x.y
> is the newer version). If that's correct, each new version of a
> dependency that contains a important fix will require *all* Python
> applications updating their versions to include the new required
> version in debian/control, if we want the user to have that fix.
>
> Mikko: feel free to correct me if I made a mistake.
Yes, you understood correctly.
> * installing this metapackage will obviously install *all* PyMaemo
> packages, which will take unnecessarily precious storage even if not
> all packages are used.
But this user/hidden (which I've never heard of) is different. It
seems that user/hidden packages get the same treatment as other user/
packages for updates, but they cannot be separately installed.
User/hidden pacakge could be part of the solution, but it's still
awkward and unnecessary hack compared to normal upgrades.
If user/hidden was used all python apps should depend on big pymaemo
metapackage, which would pull all packages even if not needed as you
said. But if user/hidden is already (or soon) there, it might be the
best option available. After all application space isn't big issue
anymore, and after installing 2-3 python application you have
practically installed all pymaemo packages anyway.
--
Mikko Vartiainen