From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH 1/2] add support for derived sbuild chroots
Date: Mon, 29 May 2023 10:14:22 +0300 [thread overview]
Message-ID: <671f33c3aa7c94457ff199c9ec2f616fdb7a7c15.camel@ilbers.de> (raw)
In-Reply-To: <20230413070026.3511123-1-felix.moessbauer@siemens.com>
On Thu, 2023-04-13 at 07:00 +0000, 'Felix Moessbauer' via isar-users
wrote:
> This patch adds support to create derived sbuild chroots to speedup
> the
> build process. For packages that share a large set of common build
> dependencies, a derived sbuild chroot can be created to avoid the
> overhead of installing all base build-deps on each sbuild invocation.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> doc/user_manual.md | 27
> +++++++++++++++++++
> meta/classes/crossvars.bbclass | 11 +++++---
> .../sbuild-chroot/sbuild-chroot.inc | 7 ++++-
> 3 files changed, 41 insertions(+), 4 deletions(-)
Despite passing CI, patch 2 has still open question. Should we merge it
or there some v2 expected?
next prev parent reply other threads:[~2023-05-29 7:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 7:00 Felix Moessbauer
2023-04-13 7:00 ` [PATCH 2/2] add example how to use " Felix Moessbauer
2023-04-14 8:46 ` Jan Kiszka
2023-06-21 12:33 ` Henning Schild
2023-05-29 7:14 ` Uladzimir Bely [this message]
2023-06-13 6:24 ` [PATCH 1/2] add support for " Uladzimir Bely
2023-06-19 5:58 ` Jan Kiszka
2023-06-19 13:10 ` Moessbauer Felix
2023-06-20 6:25 ` Uladzimir Bely
2023-06-20 8:05 ` Uladzimir Bely
2023-06-20 8:51 ` Moessbauer Felix
2023-06-21 12:42 ` Henning Schild
2023-06-21 13:22 ` Moessbauer Felix
2023-06-21 13:34 ` Henning Schild
2023-06-21 13:54 ` 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=671f33c3aa7c94457ff199c9ec2f616fdb7a7c15.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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