"ext Ville M. Vainio" <[email protected]> writes: > On Thu, Sep 9, 2010 at 11:14 AM, Andrew Flegg <[email protected]> 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.
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? :-) _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
