On Thu, Sep 9, 2010 at 11:59 AM, Marius Vollmer <marius.voll...@nokia.com> wrote:
>> This would not be completely accurate either. A manufacturer way want >> to create a special repository for packages that apps in their app >> store CAN depend on, and this is not necessarily the repository that >> the sold applications are downloaded from. > > Well, you will have a tree (or graph) of repositories, with dependencies > between repositories. This is what will happen, and if we want to do > it, we should have the tools for it and not let it happen purely > chaotically. (Remember, the Maemo repository mess? :-) I think what we need is 2 levels of repositories: 1. Blessed, curated repositories (that are configured as such in "factory" settings). With N900, this is the downloads.maemo.nokia.com repository. 2. Everything else (N900 "extras", and whatever repos users want to add). Packages in App stores will depend on packages in 1). It's the decision of phone manufacturer what repositories will belong to 1), but as long as this distinction between repositories is well specified in MeeGo spec (and bundled software - package managers come to mind, "zypper install --blessed-only"), companies won't have to do solo hacks (as done in N900, where the hacks are contained inside app manager). Specifying anything more will surely lead to analysis paralysis and manufacturers just ignoring the spec, to be able to deliver what they need. -- Ville M. Vainio @@ Forum Nokia _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
