Hi,
Just took a look at 1.0.99.3. I'd like to point out one potential issue related
to System Implementation / Platform Compliance and the MeeGo Core Packages list.
If all compliant platforms must include the binary packages listed in the MeeGo
Core Packages list, I suppose that all SW components in those packages are also
expected to be present and work in all compliant platforms (%files in spec
files not allowed to be changed)? However, as we all know, compliant platforms
can differ from each other when it comes to device/HW adaptation. Device/HW
adaptation typically consists of plugins to some user space frameworks
(GStreamer, PulseAudio, Resource Policy, Sensor Framework, oFono, X, Qt
Mobility APIs etc.) and device drivers ("plugins" to Linux kernel). And
different platforms can have a different set of HW adaptation related plugins.
Do the packages now listed in MeeGo Core Packages include device/HW adaptation
related SW components that are specific to some HW environment? E.g. do the
oFono, Sensor Framework and PulseAudio packages contain SW components that are
not applicable/sensible in all environments? If they do, isn't that a bit
problematic (components required to be present but not used/functional)? Or
have I misunderstood something?
How should we handle/mention this aspect in the compliance specification?
Regards, Jari
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of ext Wichmann, Mats D
> Sent: 26. lokakuuta 2010 20:16
> To: [email protected]
> Subject: [MeeGo-dev] Compliance spec updated 1.0.99.2
>
>
> Things still seem to be in some state of flux, but
> there's an updated edition on the page now.
>
> http://wiki.meego.com/Quality/Compliance
>
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
