The current description of IMAGE_INSTALL is still confusing when it comes to usage in local.conf. I propose changing the description as follows: 1. Declare IMAGE_INSTALL as inteded to be used only in image recipes. 2. Instead of describing the gotcha of IMAGE_INSTALL in local.conf, add reference to CORE_IMAGE_EXTRA_INSTALL which is already documented as local.conf only variable. This could be improved further by adding the CORE_IMAGE_EXTRA_INSTALL to IMAGE_INSTALL in core-image.bbclass instead of ?='ing it. This change should also be reflected on other parts of the manual in which IMAGE_INSTALL is mentioned. Related to previous changes and discussion on IMAGE_INSTALL on https://bugzilla.yoctoproject.org/show_bug.cgi?id=1897
Unfortunately CORE_IMAGE_EXTRA_INSTALL won't work for all images because it's only handled by core-image.bbclass - it won't do anything for image recipes that only inherit from image.bbclass. Can you explain what specifically you found confusing regarding setting it from local.conf?
The possibility of using +=-syntax in local.conf, which gets overwritten by most (all?) example image recipes with no warning.
There is quite a bit of explanation in the variable's description regarding the dangers of using the "+=" operator with IMAGE_INSTALL. Do we need more? I think it is pretty clear. If not, can you elaborate more? See http://www.yoctoproject.org/docs/1.9/ref-manual/ref-manual.html#var-IMAGE_INSTALL Thanks, Scott
Hi, Any further comments on this? Thanks, Scott
I am pulling this out of NEEDINFO, since Topi no longer has a valid e-mail address.
Looks like yocto-docs 834aebb75dce1c905b1e0f142d0d7de6bb44e7d4 fixed this.