From: "Ferry Toth" <fntoth@gmail.com>
To: Guillaume Champagne <champagne.guillaume.c@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 1/1] image-live.bbclass: order do_bootimg after do_rootfs
Date: Tue, 1 Jun 2021 22:12:02 +0200 [thread overview]
Message-ID: <efc2fc26-5784-8afe-b310-e5ea3b83b604@gmail.com> (raw)
In-Reply-To: <20210526183250.27433-2-champagne.guillaume.c@gmail.com>
Hi
Op 26-05-2021 om 20:32 schreef Guillaume Champagne:
> do_bootimg expects IMGDEPLOYDIR to exist, since it stores its artifacts
> there. Therefore, do_bootimg should run after do_rootfs because
> IMGDEPLOYDIR is created before do_rootfs runs since IMGDEPLOYDIR is
> contained in do_rootfs' [cleandirs] varflag.
>
> When do_bootimg depends on ${PN}:do_image_${LIVE_ROOTFS_TYPE},
> do_bootimg is correctly ordered after do_rootfs because
> do_image_${FSTYPE} tasks are added after do_image and do_image itself is
> added after do_rootfs.
>
> However, when do_bootimg doesn't depend on
> ${PN}:do_image_${LIVE_ROOTFS_TYPE}
> (introduced by: 96f47c39f1d17f073243913d524bde84add41d8f), do_bootimg
> can run before do_rootfs, thus before IMGDEPLOYDIR is created. To
> avoid this situation, do_bootimg is now explicitly ordered after
> do_rootfs.
>
> Signed-off-by: Guillaume Champagne <champagne.guillaume.c@gmail.com>
> ---
> meta/classes/image-live.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/image-live.bbclass
> b/meta/classes/image-live.bbclass
> index 8b08305cdb..fd876ed8e1 100644
> --- a/meta/classes/image-live.bbclass
> +++ b/meta/classes/image-live.bbclass
> @@ -261,4 +261,4 @@ python do_bootimg() {
> do_bootimg[subimages] = "hddimg iso"
> do_bootimg[imgsuffix] = "."
> -addtask bootimg before do_image_complete
> +addtask bootimg before do_image_complete after do_rootfs
I can not answer your question if this is the right way to go. But I'll
try this patch next weekend and return here with the results.
Thanks!
next prev parent reply other threads:[~2021-06-01 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 18:32 [RFC PATCH 0/1] image-live: order bootimg after rootfs Guillaume Champagne
2021-05-26 18:32 ` [RFC PATCH 1/1] image-live.bbclass: order do_bootimg after do_rootfs Guillaume Champagne
2021-06-01 20:12 ` Ferry Toth [this message]
[not found] ` <16848E63E6244007.7311@lists.openembedded.org>
2021-06-05 12:59 ` [OE-core] " Ferry Toth
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=efc2fc26-5784-8afe-b310-e5ea3b83b604@gmail.com \
--to=fntoth@gmail.com \
--cc=champagne.guillaume.c@gmail.com \
--cc=openembedded-core@lists.openembedded.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