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

[Marko Saukko]

On 11/18/2010 11:56 PM, Arjan van de Ven wrote:
> 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.
>

Hi,

CC'd meego-qa.

Thanks for the information. Is there pages about testing of the 
compliance? Also how it is done if the images do not even boot? Just 
comparing packages or doing chroot in the non booting image? Also is it 
done for both ARM and Intel side?

Regards,
Marko