`zypper` is not installed (no longer) in core-image-lsb-sdk images. It needs to be manually included by having "package-management" in image features. I don't actually know if zypper should be included by default or not, but there are tests covering `zypper` for lsb-sdk images.
I removed zypper deliberately from the LSB package groups since LSB does not require it - it only requires that rpm packages can be installed on the system. Adding package-management to IMAGE_FEATURES is the correct way to bring it in if we really want it for these images, but I would question whether it is necessary to have it or test it for them - particularly if we are already testing zypper in other images.
I think we should explicitly add package-management to this image
Can we justify the addition of zypper when zypper has nothing to do with LSB?
I think we are talking at cross purposes here, my guess is that that is some QA test for the -lsb image that tests zypper, which had been part of -lsb in the past. Is this maybe a test plan issue that requires package update testing on the lsb image? It might be more appropriate modify the test plan to test package management on images that contain those tools.
We'd be adding "package-management" which might add zypper, it might add opkg and so on. I think having package management in these images does make sense and was always intended. It should not explictly pull in zypper through a packagegroup dependency though.
So for "zypper" we should now read "smart" here; otherwise the issue and recommended solution are the same.
Assigning to Corneliu, to modify the LSB test plan accordingly, regarding package-management / smart testing.
Removed smart test cases from master and zypper from danny.
Verified as of 2013-02-26