| Summary: | [Hob2] Base image needs to be used rather than re-creating it | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Hob | Reporter: | Paul Eggleton <bluelightning> |
| Component: | hob | Assignee: | Cristiana Voicu <cristiana.voicu> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | alexandru.damian, andreea.b.proca, jason.wessel, jessica.zhang, jiajun.xu, poky.bs.watcher, poky.watcher, richard.purdie, sgw, song.liu |
| Version: | 1.2 | ||
| Target Milestone: | 1.4 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Paul Eggleton
2012-06-13 14:31:56 UTC
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. |