| Summary: | Clarification of IMAGE_INSTALL variable | ||
|---|---|---|---|
| Product: | [Documentation] Reference | Reporter: | Topi Kuutela <topi.kuutela> |
| Component: | handbook | Assignee: | Scott Rifenbark <srifenbark> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, poky.doc.watcher, poky.watcher, ross.burton, srifenbark |
| Version: | unspecified | ||
| Target Milestone: | 2.2 M4 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Topi Kuutela
2015-07-16 10:39:29 UTC
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. |