From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH 0/5] Separate prebuild activities
Date: Mon, 30 Oct 2023 04:44:57 +0000 [thread overview]
Message-ID: <8ba173ea9bac0fe6d381c08aeb13a49478d7f80e.camel@siemens.com> (raw)
In-Reply-To: <20230915185439.2954192-1-amikan@ilbers.de>
On Fri, 2023-09-15 at 21:54 +0300, Anton Mikanovich wrote:
> This patchset introduce three new pre-build tasks from the code was
> already
> done during the build task:
> do_dpkg_source
> do_deploy_source
We need to add sstate caching to the dpkg_source task as well.
Currently we see some significant slowdown on big source packages (like
the kernel) on otherwise fully cache-able builds.
Maybe Adriaan could add this, as he added the caching for dpkg_build as
well.
Best regards,
Felix
> do_local_isarapt
> This allows to execute tasks more efficient. On simple targets like
> qemuamd64
> the speed up of the build is around 10 second, but on complex
> downstream layers
> this effect can be more visible.
> We also introduce source packages storage in isar-apt repository
> which allows
> obtaining package Build-Depends and Provides information in Debian
> way later.
>
> Anton Mikanovich (5):
> repository: Add source package remove function
> dpkg: Limit dsc searching by workdir
> meta: Implement two stage build
> dpkg-base: Copy isar_apt to workdir in separate task
> RECIPE-API-CHANGELOG.md: Note tasks separation
>
> RECIPE-API-CHANGELOG.md | 14 +++++++++
> meta/classes/dpkg-base.bbclass | 15 +++++-----
> meta/classes/dpkg-gbp.bbclass | 2 +-
> meta/classes/dpkg-source.bbclass | 33
> ++++++++++++++++++++++
> meta/classes/dpkg.bbclass | 6 ++--
> meta/classes/repository.bbclass | 14 +++++++++
> meta/classes/rootfs.bbclass | 2 ++
> meta/recipes-kernel/linux/linux-custom.inc | 2 +-
> 8 files changed, 74 insertions(+), 14 deletions(-)
> create mode 100644 meta/classes/dpkg-source.bbclass
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-10-30 4:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 18:54 Anton Mikanovich
2023-09-15 18:54 ` [PATCH 1/5] repository: Add source package remove function Anton Mikanovich
2023-09-15 18:54 ` [PATCH 2/5] dpkg: Limit dsc searching by workdir Anton Mikanovich
2023-09-15 18:54 ` [PATCH 3/5] meta: Implement two stage build Anton Mikanovich
2023-10-12 8:48 ` Jan Kiszka
2023-10-12 9:07 ` Anton Mikanovich
2023-10-12 11:12 ` Jan Kiszka
2023-10-12 14:39 ` Baurzhan Ismagulov
2023-10-12 14:53 ` Jan Kiszka
2023-10-12 15:20 ` Baurzhan Ismagulov
2023-10-12 9:15 ` Jan Kiszka
2023-09-15 18:54 ` [PATCH 4/5] dpkg-base: Copy isar_apt to workdir in separate task Anton Mikanovich
2023-09-15 18:54 ` [PATCH 5/5] RECIPE-API-CHANGELOG.md: Note tasks separation Anton Mikanovich
2023-09-21 13:45 ` [PATCH 0/5] Separate prebuild activities Anton Mikanovich
2023-09-29 6:43 ` Uladzimir Bely
2023-10-30 4:44 ` MOESSBAUER, Felix [this message]
2023-10-30 8:00 ` Schmidt, Adriaan
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=8ba173ea9bac0fe6d381c08aeb13a49478d7f80e.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--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