public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
	isar-users@googlegroups.com, Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH v3 0/7] Migrate to mmdebstrap
Date: Tue, 20 Jun 2023 07:30:48 +0200	[thread overview]
Message-ID: <bde44218-69fc-d057-6751-c85c4dcecec0@siemens.com> (raw)
In-Reply-To: <20230531101102.101755-1-amikan@ilbers.de>

On 31.05.23 12:10, Anton Mikanovich wrote:
> Switch Isar from debootstrap to mmdebstrap.
> It makes isar-bootstrap target ~10% faster on both cross and native rootfs
> types. Also mmdebstrap support using SOURCE_DATE_EPOCH for images reproducibly
> out of the box. But the main advantage is an ability to remove sudo for
> debootstrapping later on.
> This change brakes Debian Buster support as host distro.
> 
> Changes since v2:
> - Rebase on next
> - Fix commit messages
> - Update host requirements
> 
> Changes since v1:
> - Move mmdebstrap tmpdir to workdir
> - Fix kas building
> - Improve mounts cleanup
> 
> Anton Mikanovich (5):
>   isar-bootstrap: Move preparations to hooks
>   isar-bootstrap: Use tar output instead of directory
>   user_manual.md: Replace debootstrap with mmdebstrap
>   user_manual.md: Update minimal host requirements
>   isar-bootstrap: Remove unused code
> 
> Uladzimir Bely (2):
>   meta: Switch to mmdebstrap
>   CI: Install mmdebstrap
> 
>  doc/user_manual.md                            |  41 +--
>  meta-isar/conf/distro/ubuntu-common.inc       |   4 -
>  meta/classes/rootfs.bbclass                   |  11 +-
>  .../isar-bootstrap/isar-bootstrap.inc         | 274 ++++++++----------
>  scripts/ci_build.sh                           |   6 +
>  5 files changed, 152 insertions(+), 184 deletions(-)
> 

Is this now settled? Asking as I'm planning to release kas 4.0 with the
dependencies in patch 7 resolved these days, and I'd like to see this
targeting the final version of this feature.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  parent reply	other threads:[~2023-06-20  5:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 10:10 Anton Mikanovich
2023-05-31 10:10 ` [PATCH v3 1/7] meta: Switch " Anton Mikanovich
2023-05-31 10:10 ` [PATCH v3 2/7] isar-bootstrap: Move preparations to hooks Anton Mikanovich
2023-05-31 10:10 ` [PATCH v3 3/7] isar-bootstrap: Use tar output instead of directory Anton Mikanovich
2023-05-31 10:10 ` [PATCH v3 4/7] user_manual.md: Replace debootstrap with mmdebstrap Anton Mikanovich
2023-05-31 10:11 ` [PATCH v3 5/7] user_manual.md: Update minimal host requirements Anton Mikanovich
2023-05-31 10:11 ` [PATCH v3 6/7] isar-bootstrap: Remove unused code Anton Mikanovich
2023-05-31 10:11 ` [PATCH v3 7/7] CI: Install mmdebstrap Anton Mikanovich
2023-06-20  5:30 ` Jan Kiszka [this message]
2023-06-20 10:00   ` [PATCH v3 0/7] Migrate to mmdebstrap Uladzimir Bely
2023-06-20 10:22     ` Jan Kiszka
2023-07-14 16:40     ` vijai kumar
2023-09-19  9:14     ` Schaffner, Tobias
2023-09-20  7:24       ` Uladzimir Bely
2023-09-20  7:30         ` Uladzimir Bely
2023-09-21  4:36           ` Jan Kiszka

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=bde44218-69fc-d057-6751-c85c4dcecec0@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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