If you select a base image in Hob which contains e.g. post-processing customisations, these do not get used. It seems that the base image is only used to determine the initial list of packages to be included which can be adjusted by the user, and then these selections are built as a brand new image. Ideally what should occur is that we take a copy of the selected base image and then override IMAGE_INSTALL to include the packages the user has selected, thus preserving any other functionality in the image recipe.
This is a feature, not a bug, right ?
It depends upon how you look at it. I imagine that many users would not expect the current behaviour.
Just to detail this a little bit more, the issue is that currently the system uses hob-image.bb as a base. Instead we need to take the original image recipe selected then change the included packages to match the user selection so for example, core-image-minimal has: """ IMAGE_ROOTFS_SIZE = "8192" # remove not needed ipkg informations ROOTFS_POSTPROCESS_COMMAND += "remove_packaging_data_files ; " """ and these should be included in any customised image based on core-image-minimal.
It is also the case that things like the the IMAGE_FEATURES do not get picked up from the local.conf for example. After running the hob and saving a template anything that was set in the IMAGE_FEATURES is completely gone, which is not entirely useful.
merged to master
Verified in master:4da406cd50cf02a63ed76810a670aba1eb561c79.