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

[Arjan van de Ven]

On 11/18/2010 11:36 AM, Marko Saukko wrote:
> 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? \

nope you're not quite right.

we have images that ONLY contain things needed for compliance. However 
these images will not/are not expected to even boot

and then we have core images that are the minimal set needed to be 
compliant and to boot.