Skip to content

RFC image.bbclass: support two-stage deployment of image artifacts

Bartosz Golaszewski openembedded-core 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2image.bbclass: add an intermediate deploy taskmeta/classes/image.bbclass+15 -80 replies
2/2image.bbclass: deploy artifacts in two stagesmeta/classes/image.bbclass meta/classes/image_types.bbclass meta/classes/image_types_wic.bbclass +1 more+36 -120 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH 0/2] image.bbclass: support two-stage deployment of image artifacts

From: Bartosz Golaszewski <[email protected]>

This is a follow-up to the discussion I started on the OE-core mailing list a couple days ago[1]. These patches propose to split the deployment of image artifacts into two stages where the first one includes all "regular" images and takes place before do_image_complete and the second is mostly aimed at wic right now and happens after do_image_complete.

These patches work but I'm sending them as RFC mostly to continue the discussion about possible solutions for the circular dependencies between the rootfs and initramfs.

[1] http://lists.openembedded.org/pipermail/openembedded-core/2020-March/294094.html

Bartosz Golaszewski (2):
image.bbclass: add an intermediate deploy task
image.bbclass: deploy artifacts in two stages

 meta/classes/image.bbclass                    | 54 ++++++++++++++-----
 meta/classes/image_types.bbclass              |  3 ++
 meta/classes/image_types_wic.bbclass          |  4 +-
 .../images/build-appliance-image_15.0.0.bb    |  2 +-
 4 files changed, 47 insertions(+), 16 deletions(-)
Signature · 1 line
2.19.1