From: Jan Kiszka <jan.kiszka@siemens.com>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v2 03/10] rootfs: recursively depend on packages
Date: Wed, 13 Oct 2021 16:29:23 +0200 [thread overview]
Message-ID: <b52e8015-22a5-6c5b-7dac-421960fca973@siemens.com> (raw)
In-Reply-To: <20211012123625.1703627-4-adriaan.schmidt@siemens.com>
On 12.10.21 14:36, Adriaan Schmidt wrote:
> This fixes a bug.
> So far, this only worked when the dependency-of-dependency packages
> were in isar-apt because they were just built. This explicitly
> enforces do_deploy_deb on *all* dependencies.
More curiosity: I'm not yet understanding the error scenario. A rootfs
depends on a package recipe A, and that means on the completion of that
recipe's do_deploy_deb task. If that recipe A depends on another package
recipe B that one needs to be in isar-apt, thus has to finish its
do_deploy_deb as well. But why could A have finished its build when B
didn't even run do_deploy_deb yet? If A depends on B, it also depends on
B's do_deploy_deb task, no?
Jan
>
> Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
> ---
> meta/classes/rootfs.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
> index f9151c5..bd8a241 100644
> --- a/meta/classes/rootfs.bbclass
> +++ b/meta/classes/rootfs.bbclass
> @@ -152,7 +152,7 @@ rootfs_install_pkgs_install() {
> do_rootfs_install[root_cleandirs] = "${ROOTFSDIR}"
> do_rootfs_install[vardeps] += "${ROOTFS_CONFIGURE_COMMAND} ${ROOTFS_INSTALL_COMMAND}"
> do_rootfs_install[depends] = "isar-bootstrap-${@'target' if d.getVar('ROOTFS_ARCH') == d.getVar('DISTRO_ARCH') else 'host'}:do_build"
> -do_rootfs_install[deptask] = "do_deploy_deb"
> +do_rootfs_install[recrdeptask] = "do_deploy_deb"
> python do_rootfs_install() {
> configure_cmds = (d.getVar("ROOTFS_CONFIGURE_COMMAND", True) or "").split()
> install_cmds = (d.getVar("ROOTFS_INSTALL_COMMAND", True) or "").split()
>
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-10-13 14:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 12:36 [PATCH v2 00/10] Add sstate-cache Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 01/10] oe imports in central location Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 02/10] wic-img: create deploy dir Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 03/10] rootfs: recursively depend on packages Adriaan Schmidt
2021-10-13 14:29 ` Jan Kiszka [this message]
2021-10-13 14:43 ` Schmidt, Adriaan
2021-10-13 15:09 ` Jan Kiszka
2021-10-13 15:18 ` Schmidt, Adriaan
2021-10-13 16:01 ` Jan Kiszka
2021-10-19 8:10 ` Schmidt, Adriaan
2021-10-12 12:36 ` [PATCH v2 04/10] base: remove unneeded "before do_build" task dependencies Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 05/10] dpkg: add explicit dependency to isar-apt Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 06/10] meta: add sstate feature from oe Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 07/10] sstate: configure Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 08/10] sstate: add caching to isar-bootstrap Adriaan Schmidt
2021-10-13 14:17 ` Anton Mikanovich
2021-10-19 8:11 ` Schmidt, Adriaan
2021-10-12 12:36 ` [PATCH v2 09/10] sstate: add caching to rootfs Adriaan Schmidt
2021-10-12 12:36 ` [PATCH v2 10/10] sstate: add caching to debian packages Adriaan Schmidt
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=b52e8015-22a5-6c5b-7dac-421960fca973@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@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