On Thu, Sep 16, 2010 at 19:50, Tanu Kaskinen <[email protected]> wrote: > > If no external dependencies are allowed, the device vendor only has the > burden of providing the core api. Since every device provides this api, > every compliant app is guaranteed to be able to run on the device. If a > developer wants an application to run on all Meego devices, the > developer has only one task: get the app in enough repositories so that > they together cover every Meego device.
And if they have external dependencies they have to ensure that *those* are in as many repos as possible. That's a developer problem, not a vendor problem. > If external dependencies, let's say to compliant software in the > Surrounds repo, are allowed, then the device vendor must provide access > to the Surrounds repo. That is the additional burden. Agreed. Mandating Surrounds would be a burden. What about, then, as a compromise going back to one of the earlier suggestions and saying that each repo containing MeeGo Compliant packages can depend on a well-defined set of other repos. For some vendors that may include MeeGo Surrounds; but for others it won't. > The "Meego Compliant" label won't have any value for me > personally, I'll stick to the properly packaged Extras... You're assuming that when Surrounds/Extras picks up it won't be restricted to MeeGo Compliant packages only. Cheers, Andrew -- Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ Maemo Community Council chair _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
