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

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2020-03-19 at 17:44 +0100, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> 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

This works fine until we have some new image type which then has to
depend on happening after wic. We then add a three stage process and so
on. Basically this feels like we're hardcoding something for one
specific use case which will later break and not scale to other
problems/solutions.

Sorry, I'm not convinced this is the right way to move forward. I will
try and have a think about what the right way is but sadly I don't get
much time to spend on specific problems like this :(

Cheers,

Richard