We have a slightly arbitrary split between what's in core-image.bbclass and what's in image.bbclass - this historically derives from the old Poky structure which OE-Core inherited. We need to look at whether it's appropriate to move any of these items to image.bbclass (we should certainly move PACKAGE_GROUP_package-management and then package-management can be dropped from IMAGE_FEATURES[validitems] there also).
I've sent a patch to at least move package-management over to image.bbclass; the rest will need to wait until 1.7.
Aforementioned package-management change now merged for 1.6: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=874ab5a568ddbd5b140915c1330e6513e9892666
Paul, I have a section http://www.yoctoproject.org/docs/1.9/dev-manual/dev-manual.html#remove-package-management-requirements that mentions package-management. I think we are technically okay here as we are telling the user to be sure that package-management is not in their IMAGE_FEATURES statement. It looks like the result of your patch here removed package-management from that statement. Are we okay with the "Remove Package Management Requirements" section as it is? Aside from this point, I don't know of any other potential changes to the docs for this bug once it is fixed. If there are, can you tell me? Thanks, Scott
It's too early to be sure of what documentation changes are needed. To be honest I think we have more pressing things to do so I'm going to mark this as Future for now.
Still a valid issue.
Looking at this again, it's not clear that we would move anything else from core-image to image, though we probably ought to evaluate what's in core-image to see if it still makes good sense. However we should open up a new bug when we have a bit more of a concrete idea of what we want to do.
.