[maemo-developers] Community updates for diablo (specifically Application Manager if nothing else)

[From: Marius Vollmer]

ext Andrew Flegg <andrew at bleb.org> writes:

> The only thing I'd like to see is if we can *push* to users an update
> which will turn on osso-software-version-rx* updates from maemo.org
> Extras.

Ah, yes, I missed the "push" aspect.

> I'm not holding my breath, in which case the number of users
> who will benefit from this update will be the smaller, self-selecting
> set of users who choose to install the package.

Yes.  Hmm.  I think this can go on in parallel: the special package
needs to exist anyway and initially people are required to install it
explicitly.  Once it exists and some people use it, it should be easier
to convince Nokia to give it an official blessing by pushing the special
package out from the nokia-system domain.

> Carsten suggested that the install link on
> http://wiki.maemo.org/Extras could include a declaration of wanting
> "maemo-community-updates"

Hmm, this all is only applicable to Diablo, you wouldn't want to do it
for Fremantle.  Extras itself applies to Diablo and Fremantle at the
some time, no?

> - all it'll do, from the sound of it, is increase the trust level of
> "maemo-extras" (I wouldn't even make it certified, if that could be
> avoided).

It can be avoided, just don't put the <certified/> element into it.

You can also include maemo-community-updates as a dependency in the
first community version of osso-software-version-rx* and tell people to
install it in red-pill mode.  That might be less confusing since
maemo-community-updates need not be mentioned in the instructions then.

(In red-pill mode, the AM will allow package domain violations, after
explicit confirmation from the user.)