On Sep 14, 2010, at 11:47 PM, ext Attila Csipa wrote: On Tue, Sep 14, 2010 at 10:19 PM, Skarpness, Mark <mark.skarpn...@intel.com<mailto:mark.skarpn...@intel.com>> wrote: Allowing applications to have arbitrary external dependencies that are resolved at install time adds a great deal of complexity and uncertainty for a device manufacturer (substitute "MeeGo software stack provider" for "device manufacturer" if you wish).
I want to create a simple "contract" between the device manufacturer and the application developer: the device manufacturer promises to provide a defined set of packages and the application promises to install and run correctly using only those packages. And how this contract is broken if there is well maintained extras library where game developer can download as example box2d or some other qwt library etc ? If library libx is MooGo compliant, and application A depends on libx, how application A is not MeeGo compliant, how will things change if libx is maintained in quality controlled external repository and not hacked by application developer to same package ? How having extras repository adds any uncertainty or complexity to device manufacturer ? If extras repository has peer based quality control i think that this actually reduces uncertainty or complexity when community has already made quality control for library. Kate
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
