public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v1 0/6] Migrate to mmdebstrap
Date: Fri, 12 May 2023 21:50:29 +0200	[thread overview]
Message-ID: <20230512215029.69351b38@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230509082107.1657595-1-amikan@ilbers.de>

Am Tue,  9 May 2023 11:21:01 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:

> 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.

Maybe you can add a few words on the relevance and the sustainability
of mmdebstrap and compare it to debootstrap. Is it an official debian
supported tool, where does upstream use it, do we align with debian
strategy here?

As far as i remember we came from multistrap and eventually switches to
debootstrap. And the reasons have been around multistrap being somehow
not official or sustainable.

Maybe that is in the commits, i am starting the review at the
cover-letter.

Henning

> Anton Mikanovich (4):
>   isar-bootstrap: Move preparations to hooks
>   isar-bootstrap: Use tar output instead of directory
>   user_manual.md: Replace debootstrap with mmdebstrap
>   isar-bootstrap: Remove unused code
> 
> Uladzimir Bely (2):
>   meta: Switch to mmdebstrap
>   CI: Install mmdebstrap
> 
>  doc/user_manual.md                            |   4 +-
>  meta-isar/conf/distro/ubuntu-focal.conf       |   4 -
>  meta/classes/rootfs.bbclass                   |  11 +-
>  .../isar-bootstrap/isar-bootstrap.inc         | 269
> ++++++++---------- scripts/ci_build.sh                           |
> 6 + 5 files changed, 133 insertions(+), 161 deletions(-)
> 


  parent reply	other threads:[~2023-05-12 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  8:21 Anton Mikanovich
2023-05-09  8:21 ` [PATCH v1 1/6] meta: Switch " Anton Mikanovich
2023-05-09  8:21 ` [PATCH v1 2/6] isar-bootstrap: Move preparations to hooks Anton Mikanovich
2023-05-09  8:21 ` [PATCH v1 3/6] isar-bootstrap: Use tar output instead of directory Anton Mikanovich
2023-05-09  8:21 ` [PATCH v1 4/6] user_manual.md: Replace debootstrap with mmdebstrap Anton Mikanovich
2023-05-10  7:09   ` Jan Kiszka
2023-05-10  7:15     ` Anton Mikanovich
2023-05-18  6:31     ` Anton Mikanovich
2023-05-09  8:21 ` [PATCH v1 5/6] isar-bootstrap: Remove unused code Anton Mikanovich
2023-05-09  8:21 ` [PATCH v1 6/6] CI: Install mmdebstrap Anton Mikanovich
2023-05-12 19:50 ` Henning Schild [this message]
2023-05-29 14:06   ` [PATCH v1 0/6] Migrate to mmdebstrap Baurzhan Ismagulov
2023-05-12 20:07 ` Henning Schild
2023-05-18  6:39   ` Anton Mikanovich

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=20230512215029.69351b38@md1za8fc.ad001.siemens.net \
    --to=henning.schild@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