Hi,
Following on from Marius Vollmer's comments in #3845[1] - "New list of
valid categories needs to be added to Application Manager [...]", this
is an attempt to start the discussion on how (and *if*) we can do as
he outlines:
> Still, I think the best way forward is for the community to take
> ownership of Diablo, and to produce the next release.
Matan Ziv-Av also started an earlier discussion on this:
http://www.mail-archive.com/maemo-developers@maemo.org/msg17133.html
> Since the http://catalogue.tableteer.nokia.com/updates/diablo/ is,
> *cough*, stable now, it can be used as the basis for a community
> distribution.
>
> Depending on how brave we want to be, it is even feasible now to
> start offering new Diablo releases from Maemo Extras.
I want to be this brave; if we can get notional sign-off from Quim -
and it's technically achievable in an end-user friendly way.
> I think the following could work:
>
> - We start signing Diablo Maemo Extras.
Some interesting practical questions:
* How owns the key? The maemo.org debmaster (i.e. Jeremiah) is an
obvious example; with copies also held by the council and the
X-Fade?
* AIUI, the only technical step here is to sign the Release file
with the GPG key.
> - We put a "maemo-community-archive-keyring" package or something into Diablo
> Maemo Extras that contains the public key needed to verify the signature.
> It also contains a new "package domain" with a trust level of 600.
The "package domain"s are entirely Application Manager specific, IIRC?
Does "sort-weight" in nokia-repository's postinst correspond to the
"trust level"?
> Installing this package will configure the Application manager so that it
> allows updating OS packages from Maemo Extras.
>
> - We start putting new packages into Maemo Extras, such as the new
> Application manager.
>
> - We make release new osso-software-version meta packages or we
> improve the Application Manager to not need meta packages.
First step, I'd suggest would be a small rollout:
* hildon-application-manager 1:2.1.xx-community (where xx > 19)
* hildon-application-manaer-l10n 5.1-community
* osso-software-version-rx* 1:6.2009.nn-community
The only code change would be those from h-a-m with the grid view and
the i18n fix. The l10n package would be built up from the strings in
the package page[2].
If this works, we can then look to any future enhancements we want to make.
> If Diablo Maemo Extras doesn't seem to be the right place for this, any other
> repository will do as well, of course.
I think it's the right place, since Extras is the key repository
containing the packages. Outstanding questions which a more "official"
Nokia position on would be good (Quim?):
* Is there _any_ chance of getting "maemo-community-archive-keyring"
shipped through Tableteer, and so being more actively pushed out
to users as part of an SSU?
* If we are careful to not change the fundamental behaviour of the
system, are Nokia happy with the community pushing out individual
updates to system components via SSU, using the above mechanism?
In particular, I don't think we should use this power (if able to us)
to bulk-update everyone to Mer in about 6 months' time ;-)
Cheers,
Andrew
[1] https://bugs.maemo.org/show_bug.cgi?id=3845#c11
[2] http://wiki.maemo.org/Task:Package_categories#Translations
--
Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
