On Tue, Apr 14, 2009 at 17:01, Marius Vollmer <[email protected]> wrote:
>
> Package domains are 'orthogonal' to catalogues and repositories. They
> are connected by the signature of the Release file.
>
> The AM looks at the keys that have been used to sign the Release file
> and associates each package with a package domain. Package domains are
> configured in /etc/hildon-application-manager/domains. You will find
> the trust level in there, among other things.
So the key is the key. All of the entries on my N810 have *two* "key"
elements per entry, and there's already one for "maemo-extras"
(although maemo.org Extras for diablo's Release file is not signed).
Some questions:
* The name of a domain is only to allow manipulation with
hildon-application-manager-config?
* What is the effect of two "key" elements against a domain entry?
How would they have got there?
* Any ideas where the "maemo-extras" one has come from?
>> 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
>
> I would lose the "community" suffix, actually. The
> osso-software-version-rx* package could get a display name that clearly
> spells out that this is not from Nokia.
Fair enough. I suppose the only outstanding question is whether Nokia
will push out one last SSU to include the "maemo-community-updates"
package which correctly sets up the package domain for maemo.org
Extras.
Once we've got this sorted, I'm happy to produce and push the various
packages (assistance always welcome, of course - especially with the
osso-software-version-rx*). If we move quickly, we can work within the
timescales Ryan's suggesting for the transition to the new package
categories:
http://lists.maemo.org/pipermail/maemo-developers/2009-April/054566.html
Cheers,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
maemo-developers mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-developers