public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH 2/6] meta/isar-bootstrap: allow passing a SCRIPT to debootstrap
Date: Mon, 14 Dec 2020 08:11:23 +0100	[thread overview]
Message-ID: <d00f407d8935566f0b53d8085547e31107ef50ea.1607929886.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1607929886.git.jan.kiszka@siemens.com>

From: Henning Schild <henning.schild@siemens.com>

Debootstrap uses scripts that usually have the same name as SUITE so we
never set them. In order to install a SUITE that an outdated version of
debootstrap does not (yet) know, we can tell debootstrap which SCRIPT to
use.
In fact many modern SUITEs will use SCRIPTS we might already have, we
just do not have the symlink to them.
i.e. "cosmic" uses the SCRIPT "gutsy" and a debootstrap from "stretch"
does know "gutsy" but not "cosmic"
So we can debootstrap SUITEs from the future, given they use a SCRIPT we
already have.

Signed-off-by: Henning Schild <henning.schild@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
index dca136e0..a5cd1f03 100644
--- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
+++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
@@ -271,14 +271,16 @@ isar_bootstrap() {
                                ${@get_distro_components_argument(d, True)} \
                                "${@get_distro_suite(d, True)}" \
                                "${ROOTFSDIR}" \
-                               "${@get_distro_source(d, True)}"
+                               "${@get_distro_source(d, True)}" \
+                               ${DISTRO_DEBOOTSTRAP_SCRIPT}
             else
                 ${DEBOOTSTRAP} $debootstrap_args \
                                --arch="${DISTRO_ARCH}" \
                                ${@get_distro_components_argument(d, False)} \
                                "${@get_distro_suite(d, False)}" \
                                "${ROOTFSDIR}" \
-                               "${@get_distro_source(d, False)}"
+                               "${@get_distro_source(d, False)}" \
+                               ${DISTRO_DEBOOTSTRAP_SCRIPT}
             fi
 
             # Install apt config
-- 
2.26.2


  parent reply	other threads:[~2020-12-14  7:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14  7:11 [PATCH 0/6] Add support for Ubuntu Jan Kiszka
2020-12-14  7:11 ` [PATCH 1/6] meta: image: Account for Ubuntu differences in do_copy_boot_files Jan Kiszka
2020-12-14 12:16   ` Henning Schild
2020-12-14 12:27     ` Jan Kiszka
2020-12-14 12:36       ` Henning Schild
2020-12-14 16:39         ` Jan Kiszka
2020-12-14 16:40           ` Henning Schild
2020-12-15  9:22             ` Jan Kiszka
2020-12-14  7:11 ` Jan Kiszka [this message]
2020-12-14  7:11 ` [PATCH 3/6] wic: bootimg-efi-isar: Add support for Ubuntu Jan Kiszka
2020-12-14 12:13   ` Henning Schild
2020-12-14 12:28     ` Jan Kiszka
2020-12-14 12:33       ` Henning Schild
2020-12-14  7:11 ` [PATCH 4/6] meta: cache_deb_src: Account for the case that resolv.conf is a non-existent link Jan Kiszka
2020-12-14  7:11 ` [PATCH 5/6] meta-isar: Add new distro ubuntu with suite "focal" Jan Kiszka
2020-12-14  7:11 ` [PATCH 6/6] meta-isar: linux-mainline: Adjust cfg fragment test to arm64 defconfig Jan Kiszka
2020-12-14 12:06 ` [PATCH 0/6] Add support for Ubuntu Henning Schild
2020-12-14 12:26   ` Jan Kiszka
2021-01-18 16:15 ` 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=d00f407d8935566f0b53d8085547e31107ef50ea.1607929886.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=henning.schild@siemens.com \
    --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