On Thu, 2010-09-16 at 20:42 +0100, Andrew Flegg wrote: > 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.
Hmm... For some reason I didn't consider this - I sort of assumed that if some library is in Surrounds, then every device must get it from Surrounds. But like applications, libraries can of course also be published in multiple repositories. This may cause some problems with different versions of the same package being available in different repositories, but the big fragmentation problem that I was presenting doesn't really exist, as far as I can see. I'm back in the "allow dependencies" camp. -- Tanu Kaskinen _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
