public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Bartosz Golaszewski" <brgl@bgdev.pl>
To: Khem Raj <raj.khem@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	Armin Kuster <akuster808@gmail.com>,
	Jerome Neanne <jneanne@baylibre.com>,
	Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: openembedded-core@lists.openembedded.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [OE-core][PATCH v2 0/2] introduce multi-state image deployment
Date: Mon,  6 Apr 2020 19:02:27 +0200	[thread overview]
Message-ID: <20200406170229.25363-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bgolaszewski@baylibre.com>

Hi Richard et al,

This is another shot at multi-stage image deployment. This time around
I managed to fix the problem with changing task hashes and anonymous
python functions ordering by simply moving the code assigning pre- and
postfuncs for sstate into an even handler invoked right after all
anonymous python code is run. Seems to work fine and there's no need
to deltask do_package anymore.

Just like before: each image task becomes an sstate task and handles
the deployment of the artifacts it generates. Files created by tasks
other than IMAGE_CMD are still deployed by do_image_complete.

The dm-verity problem I'm trying to solve is described here:
    https://lists.openembedded.org/g/openembedded-core/message/136203

Bartosz Golaszewski (2):
  qemuboot.bbclass: don't redefine IMGDEPLOYDIR
  image.bbclass: deploy image artifacts in stages

 meta/classes/image.bbclass    | 17 +++++++++++++++++
 meta/classes/qemuboot.bbclass |  1 -
 meta/classes/sstate.bbclass   |  4 ++++
 3 files changed, 21 insertions(+), 1 deletion(-)

-- 
2.25.0


             reply	other threads:[~2020-04-06 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 17:02 Bartosz Golaszewski [this message]
2020-04-06 17:02 ` [OE-core][PATCH v2 1/2] qemuboot.bbclass: don't redefine IMGDEPLOYDIR Bartosz Golaszewski
2020-04-06 17:02 ` [OE-core][PATCH v2 2/2] image.bbclass: deploy image artifacts in stages Bartosz Golaszewski
2020-04-15 10:20   ` Bartosz Golaszewski
2020-04-15 10:32     ` Richard Purdie
2020-04-15 11:14       ` Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200406170229.25363-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=akuster808@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=jneanne@baylibre.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox