Bug 10203 - prefer specialized image creation methods over chaining
Summary: prefer specialized image creation methods over chaining
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 2.3
Hardware: All Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-09-01 15:01 UTC by Patrick Ohly
Modified: 2026-08-13 14:59 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Ohly 2016-09-01 15:01:51 UTC 
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