<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>Hi
<br>
<br>----- Alkuperäinen viesti -----
<br>> On Fri, Dec 18, 2009 at 3:14 PM, Niels Breet <<a href="mailto:niels@maemo.org">niels@maemo.org</a>> wrote:
<br>> > Developers have python available in SDK and also know how to handle either
<br>> > red-pill or apt-get.
<br>>
<br>> So, If I understand correctly, developers (even newcomers to the Maemo
<br>> world) should have extras-devel enabled on their devices for
<br>> development? Otherwise they would not have access to e.g. bindings
<br>> that are not used yet (and thus did not get promoted to extras).
<br>>
<br>> I did this on a N900 and I saw many updates appearing for applications
<br>> not related to my development work. Most probably the new versions
<br>> were coming from extras-devel. Wouldn't that be confusing to new N900
<br>> developers?
<br>
<br>Yes. I usually have extras-devel disabled to avoid unwanted updates. I enable it only when I need to install something from there. Somekind of option to ignore updates from selected repositories would be usefull. Is something like this currently possible?
<br>
<br>
<br>>
<br>> > Until we have the repository/library maintainer track sorted out, I
<br>> > propose to follow these steps:
<br>> >
<br>> > - If you are not listed as maintainer for an existing library and still
<br>> > want to have it updated, contact the maintainer. If the maintainer is not
<br>> > available or doesn't respond, mail to maemo-developers list.
<br>> > *** Please don't update a library maintained by anybody else without
<br>> > consent or public discussion***
<br>> > - The maintainer/author uploads new version, checks if applications using
<br>> > the app still work correctly.
<br>> > - Ping me or mail -developers to push it through manually to testing. Here
<br>> > we can all do a final test to see if nothing breaks.
<br>>
<br>> Sounds reasonable IMHO. Is that also the case if some package needs to
<br>> be "demoted" from extras-testing?
<br>>
<br>> > I hope to have an interface for maintainers available in the beginning of
<br>> > the new year.
<br>>
<br>> Good to hear that! Will it be not restricted just to user/* applications?
<br>>
<br>> > This doesn't solve the problem that the Application manager doesn't update
<br>> > libraries on their own though. That problem should be a separate
<br>> > discussion.
<br>>
<br>> Agreed. One thing I noticed is that removing some application using
<br>> Application Manager does not remove its unused dependencies (e.g. like
<br>> "apt-get autoremove" does). So the device tends to get filled up with
<br>> unused dependencies, with no user-friendly way of removing them. Did
<br>> anyone else notice this?
<br>
<br>
<br>BR
<br>
<br>-Timo</p>
</body>
</html>