[maemo-developers] Pushing optified Python libs

[From: Anderson Lizardo]

On Fri, Dec 18, 2009 at 3:14 PM, Niels Breet <niels at maemo.org> wrote:
> Developers have python available in SDK and also know how to handle either
> red-pill or apt-get.

So, If I understand correctly, developers (even newcomers to the Maemo
world) should have extras-devel enabled on their devices for
development? Otherwise they would not have access to e.g. bindings
that are not used yet (and thus did not get promoted to extras).

I did this on a N900 and I saw many updates appearing for applications
not related to my development work. Most probably the new versions
were coming from extras-devel. Wouldn't that be confusing to new N900
developers?

> Until we have the repository/library maintainer track sorted out, I
> propose to follow these steps:
>
> - If you are not listed as maintainer for an existing library and still
> want to have it updated, contact the maintainer. If the maintainer is not
> available or doesn't respond, mail to maemo-developers list.
> *** Please don't update a library maintained by anybody else without
> consent or public discussion***
> - The maintainer/author uploads new version, checks if applications using
> the app still work correctly.
> - Ping me or mail -developers to push it through manually to testing. Here
> we can all do a final test to see if nothing breaks.

Sounds reasonable IMHO. Is that also the case if some package needs to
be "demoted" from extras-testing?

> I hope to have an interface for maintainers available in the beginning of
> the new year.

Good to hear that! Will it be not restricted just to user/* applications?

> This doesn't solve the problem that the Application manager doesn't update
> libraries on their own though. That problem should be a separate
> discussion.

Agreed. One thing I noticed is that removing some application using
Application Manager does not remove its unused dependencies (e.g. like
"apt-get autoremove" does). So the device tends to get filled up with
unused dependencies, with no user-friendly way of removing them. Did
anyone else notice this?

Regards,
-- 
Anderson Lizardo
OpenBossa Labs - INdT
Manaus - Brazil