From: Henning Schild <henning.schild@siemens.com>
To: <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: Re: [PATCHv2 2/2] sstate: fix task order and deps
Date: Fri, 28 Jan 2022 10:12:06 +0100 [thread overview]
Message-ID: <20220128101206.35c50e07@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220128090010.13589-3-henning.schild@siemens.com>
Am Fri, 28 Jan 2022 10:00:10 +0100
schrieb Henning Schild <henning.schild@siemens.com>:
> With do_rootfs_install being the new sstate task we need to be more
> precise on what needs to happen before do_rootfs_postprocess.
>
> Some postprocess functions need files downloaded so we add "after
> unpack"
> - sdkchroot_install_files
> - buildchroot_install_files
> And do_rootfs_postprocess needs the apt caches for rootfs_do_mounts.
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> meta/classes/rootfs.bbclass | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
> index 78fb2cc71350..9f0d345dae03 100644
> --- a/meta/classes/rootfs.bbclass
> +++ b/meta/classes/rootfs.bbclass
> @@ -262,7 +262,7 @@ python do_rootfs_postprocess() {
> bb.build.exec_func(cmd, d)
> progress_reporter.update(int(i / len(cmds) * 100))
> }
> -addtask rootfs_postprocess before do_rootfs
> +addtask rootfs_postprocess before do_rootfs after do_unpack
>
> python do_rootfs() {
> """Virtual task"""
> @@ -270,9 +270,10 @@ python do_rootfs() {
> }
> addtask rootfs before do_build
>
> +do_rootfs_postprocess[depends] = "base-apt:do_cache
> isar-apt:do_cache_config" +
i do understand why this needs to be here, and it is in the commit
message.
> SSTATETASKS += "do_rootfs_install"
> ROOTFS_SSTATE = "${WORKDIR}/rootfs-sstate"
> -do_rootfs_install[depends] += " base-apt:do_cache
> isar-apt:do_cache_config" do_rootfs_install[dirs] +=
However i do not fully understand why it seems ok to drop this again.
All test i did so far look promising. And i rather not have deps
overspecified, that is why i drop it here.
Henning
> "${ROOTFS_SSTATE} ${WORKDIR}/mnt/rootfs" do_rootfs_install[cleandirs]
> += "${ROOTFS_SSTATE}" do_rootfs_install[sstate-plaindirs] =
> "${ROOTFS_SSTATE}"
prev parent reply other threads:[~2022-01-28 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 9:00 [PATCHv2 0/2] sstate bug fix Henning Schild
2022-01-28 9:00 ` [PATCHv2 1/2] sstate: change rootfs task to cache Henning Schild
2022-01-28 9:00 ` [PATCHv2 2/2] sstate: fix task order and deps Henning Schild
2022-01-28 9:12 ` Henning Schild [this message]
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=20220128101206.35c50e07@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
/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