[MeeGo-dev] Meego spec - for comment
tim at framstag.com
Thu Sep 16 14:23:41 PDT 2010
> Imagine that Nokia ship Extras and Ovi enabled in all their devices.
> bobapp is in Ovi, and can be in MeeGo Compliant as only Nokia devices
> can have Ovi and all Nokia devices have Extras available and enabled
> to provide their dependencies.
> However, if the bobapp developer uploaded the package to another repo,
> it may not be Compliant, as the covenant that it's dependencies MUST
> be resolvable isn't met. Then, the developer would have to upload the
> source packages (or binary) from Extras to that third party repo as
> well; or link them in statically.
This however means that there can be no central instance to decide if an
application is compliant or not just based on the application package
and its contents and thus an applications compliance is in relation to
the platform it is running.
So bobapp's web page and package description would say:
* This is the wonderful bobapp. It is Meego compliant for Device Zupp
and Device Wusch but not for Device ExtraLess.
Is this the kind of complicance statement that e.g. marketing has
ordered ;-)? Would such compliance statement be of any help?
More information about the MeeGo-dev