From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH 1/1] rootfs: remove temporary sstate deploy directory after task execution
Date: Mon, 23 Feb 2026 13:43:24 +0000 [thread overview]
Message-ID: <fd505a40fb9fda75a301d652fa2e468ceb0056f5.camel@siemens.com> (raw)
In-Reply-To: <20260223133255.1025809-1-felix.moessbauer@siemens.com>
On Mon, 2026-02-23 at 14:32 +0100, Felix Moessbauer wrote:
> The rootfs_install_sstate_prepare currently leaves an empty directory
> skeleton behind. As this does not have any value for debugging, we
> remove it.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/classes-recipe/rootfs.bbclass | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/classes-recipe/rootfs.bbclass b/meta/classes-recipe/rootfs.bbclass
> index 73ffa6b2..9044bf93 100644
> --- a/meta/classes-recipe/rootfs.bbclass
> +++ b/meta/classes-recipe/rootfs.bbclass
> @@ -662,6 +662,8 @@ rootfs_install_sstate_prepare() {
> # tar --one-file-system will cross bind-mounts to the same filesystem,
> # so we use some mount magic to prevent that
> mkdir -p ${WORKDIR}/mnt/rootfs
> + trap 'rmdir ${WORKDIR}/mnt/rootfs ${WORKDIR}/mnt' EXIT
> +
PS: I found this while working on the rootless series. I just noticed,
that this patch does not apply as-is on isar next, but the idea behind
it should be clear.
Felix
> run_privileged_heredoc <<'EOF' 3> rootfs.tar
> mount -o bind,private '${ROOTFSDIR}' '${WORKDIR}/mnt/rootfs' -o ro
> lopts="--one-file-system --exclude=var/cache/apt/archives"
> --
> 2.51.0
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/fd505a40fb9fda75a301d652fa2e468ceb0056f5.camel%40siemens.com.
next prev parent reply other threads:[~2026-02-23 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 13:32 'Felix Moessbauer' via isar-users
2026-02-23 13:43 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-02-26 16:09 ` Zhihang Wei
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=fd505a40fb9fda75a301d652fa2e468ceb0056f5.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.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