On Saturday 18 September 2010 20:58:23 Carsten Munk wrote: > If you have an API you'd like to share with the world, put it in > Staging and take responsibility for it.
But not all the packages that form part of an Application will be built from the same source package or be suitable for general use by the world. Consider any "suite" of related applications (e.g. an office suite or a set of games using a common engine or the GPE suite). These will generally consist of several apps (of which the user may install one or more) and several libraries which support those apps but which are "internal" to the suite. For example, if I created a suite of apps to read and write Microsoft Office files I would certainly create libraries to handle the various file formats and then access them from my documents, spreadsheets and presentation applications. You are saying these apps could not be MeeGo Compliant unless the libraries were all put in Staging (and, presumably, proposed for future inclusion in MeeGo). But that condition is unreasonable: the app developer may not be willing to offer support to anyone outside his own project using the libraries -- that shouldn't stop his app being Compliant. > * Remove all dependencies which originate from the installation source > and is produced by the same source package as application A workable condition might be to say "maintained by the same maintainer" (instead of "produced by the same source package"). In that case, we would still be able to avoid the problem of someone else making incompatible changes to the library (because it is owned by the same person who owns the app). > There is the problem of Staging that app stores that do not allow > other installation sources than themselves would have trouble. The > solution is obviously that Staging repo inclusion is part of MeeGo > compliance for dependency solving, but we're not quite there yet to > convince this is worthwhile. Personally I don't think Staging is needed as part of the Compliance definition (it might be needed for other reasons). The rule should be: an app can depend on any other package which is maintained by the same entity (person/company/project team/whatever) and which is available from the same repository. If an app store doesn't make packages available as a repository (for example it sends an RPM to the device) then the app-store app on the device would have to be extended very slightly to be able to receive multiple rpms (for example as a zipfile or tar file), split them out and install all of them. This is not a heavyweight requirement for any device vendor (MeeGo could even provide example code). Graham _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
