[Meego-architecture] What should be in MeeGo Core images?

Marko Saukko marko.saukko at cybercom.com
Thu Nov 18 03:36:51 PST 2010


Hi,

I want to raise a discussion how the core images should look like. 
Currently there are two core images available for core-armv7l-n900 as 
well as core-ia32-generic, which are both available at 
http://meego.gitorious.org/meego-os-base/image-configurations/trees/master/core 
Between these two kickstarts there are some differences which makes the 
images different. We should try to keep these .ks files as similar as 
possible to provide more consistent test results between the two 
architectures.

If I have understood correctly the Core image should contain all of the 
requirements of MeeGo Compliance and nothing else so we could verify 
that the compliance group and packages in compliance group are doing 
what they are expected. Am I right about this assumption?

Anyway every and each package that are introduced to the image may 
fix/break some of the test results. Example: If compliance group would 
not include package X and in kickstart there would be package Y 
installed that requires the package X and thus the package X would be 
installed. Then the failure in "compliance group" would not be noticed 
with this specific core image. There are some specific packages that are 
required by QA or something, but those packages should be handled one by 
one.

If I have understood correctly the package groups that should be 
included in core images to provide packages from core up to MeeGo API:

@MeeGo Core
@MeeGo Base
@Minimal MeeGo X Window System
@MeeGo Compliance

And the platform specific packages are needed as well

N900:
@Nokia N900 Support
@Nokia N900 Proprietary Support

Netbook:
@X for Netbooks
kernel-netbook

Then all the rest except these packages mentioned above should be 
removed if there isn't very good reason why they are there. Currently in 
N900 core image there are tools that were requested by testing people 
and in netbook core kickstart there are libmeegotouch packages which 
bring also the UX components to the image.

So what should be in core image?

Regards,
Marko Saukko


More information about the MeeGo-architecture mailing list