| Summary: |
prefer specialized image creation methods over chaining |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Patrick Ohly <patrick.ohly> |
| Component: |
deployment | Assignee: |
Unassigned <unassigned> |
| Status: |
NEW
---
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
kexin.hao, randy.macleod, tim.orling
|
| Version: |
2.3 | |
|
| Target Milestone: |
Future | |
|
| Hardware: |
All | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Yes (doc changes required)
|
|---|
If a certain image type can be created both by applying conversion commands to a base type as well as via a specialized command (like a fictitious IMAGE_CMD_ext4.xz, or some dedicated task, as indicated by IMAGE_TYPES_MASKED = ext4.xz), then it is better to start with the specialized command or task. That way developers can choose between using the builtin conversion support or re-implementing certain types, for example more efficiently without intermediate files. Out-dated patch is here: https://github.com/pohly/ostro-os/commit/be80d9330cccb496653d5c08b218b6e50e05b729