From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: Avoid to create the rootfs tarball saves almost 5 minutes
Date: Thu, 20 Oct 2022 13:09:01 +0200 [thread overview]
Message-ID: <20221020130901.31ff5121@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO5-fNhXMtFZ+rP=jr9BOMJFBFpBWoT14S6vaGeCYhLchw@mail.gmail.com>
Am Thu, 20 Oct 2022 07:50:48 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> Hi all,
>
> I wish to have your opinion about this change that I have tried
What are you trying to do?
I have a nicer one, map build complete to "/bin/true" and i am ready in
no time. Also saves a ton of disk space.
Maybe you are looking for SSTATE_SKIP_CREATION ?
Henning
> clean isar
> build complete
>
> real 20m42,463s
> user 0m0,229s
> sys 0m0,152s
>
> * 1894555 - rootfs_install_sstate_prepare does nothing
> This commit avoid to create the rootfs tarball
>
> clean isar
> build complete
>
> real 16m7,703s
> user 0m0,151s
> sys 0m0,140s
>
> clean isar
> build complete
>
> real 16m6,141s
> user 0m0,124s
> sys 0m0,149s
>
>
> diff --git a/recipes-core/images/eval-image-template.inc
> b/recipes-core/images/eval-image-template.inc
> index 48bfc01..86b761d 100644
> --- a/recipes-core/images/eval-image-template.inc
> +++ b/recipes-core/images/eval-image-template.inc
> @@ -23,3 +23,7 @@ IMAGE_INSTALL += "expand-on-first-boot"
>
> WIC_IMAGER_INSTALL += "btrfs-progs"
> WIC_DEPLOY_PARTITIONS = "0"
> +
> +rootfs_install_sstate_prepare() {
> + true
> +}
>
> Thanks, R-
>
next prev parent reply other threads:[~2022-10-20 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 5:50 Roberto A. Foglietta
2022-10-20 11:09 ` Henning Schild [this message]
2022-10-20 11:15 ` Roberto A. Foglietta
2022-10-20 12:18 ` Henning Schild
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=20221020130901.31ff5121@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@gmail.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