On Thu, Sep 9, 2010 at 11:14 AM, Andrew Flegg <and...@bleb.org> wrote:
> That's why I'm proposing that the language in the spec recognises that > MeeGo-compliant packages can have a canonical location (e.g. > "repository X") and can depend on anything else in that repository. 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. All of this will probably end up so that: - There will be a bunch of "meego compliant" applications that only depend on what is already in meego - There will be a bunch of noncompliant applications that will, nevertheless, be sold in app stores. MeeGo implementation should be compliant with meego spec even if it allows installation & sales of apps like this. -- Ville M. Vainio @@ Forum Nokia _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
