public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: <kazuhiro3.hayashi@toshiba.co.jp>
Cc: <isar-users@googlegroups.com>, <meta-eid@googlegroups.com>
Subject: Re: multistrap support
Date: Wed, 13 Feb 2019 16:18:59 +0100	[thread overview]
Message-ID: <20190213161859.24c4df54@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <OSAPR01MB46915F28FC52AFF1D3CDFFB4E1660@OSAPR01MB4691.jpnprd01.prod.outlook.com>

Hi,

in fact Isar does not really care too much about how exactly
setup_root_file_system does what it does. Just the interface has to be
stable at some point. So you take a list of repos and packages and off
you go ... to put it overly-simple.

rootfs = strap(repos, package-names)

That is why the switch from multistrap to debootstrap was relatively
simple. So you could even think about switching back or switching to
yet another <funny>-strap.

What i would like to understand is why you care about multistrap and
why you think the strap-tool has an implication on collaboration with
other projects? Where do you see the risk of not being able to share
efforts with other projects that use multistrap?

Henning

Am Wed, 13 Feb 2019 13:14:57 +0000
schrieb <kazuhiro3.hayashi@toshiba.co.jp>:

> Hi,
> 
> I would like to know if isar still has some plans to use multistrap
> again (or similar existing tools if exists) to generate target images.
> 
> Multistrap for isar-image-base has been removed by the following
> commit:
> https://github.com/ilbers/isar/commit/19a314559178f7afd93ce3dafe8c8647ca6c8884
> and replaced by setup_root_file_system() in
> isar-bootstrap-helper.bbclass, which seems to use (pre-built?)
> isar-bootstrap-$ROOTFS_DISTRO-$ROOTFS_ARCH as the base tree instead
> of running the debootstrap process.
> 
> I guess that the main purposes of quitting multistrap is that
> there is no big update for a few years (though the last update is
> 2.2.10 on Nov. 2018) Are there any other reasons?
> (Some bugs difficult to be fixed, mismatches with isar specification,
> etc.)
> 
> The current isar-bootstrap based approach would work fine for isar
> system, but in that case, it might be difficult to share efforts for
> developing and maintaining the functionality with non isar users.
> I'm just interested in the future plan of isar.
> 
> Kind regards,
> Kazu
> 
>  Kazuhiro Hayashi
>  Corporate Software Engineering & Technology Center
>  Toshiba Corporation
>  Tel: +81-44-549-2476
>  E-mail: kazuhiro3.hayashi@toshiba.co.jp
> 
> 


  parent reply	other threads:[~2019-02-13 15:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 13:14 kazuhiro3.hayashi
2019-02-13 13:56 ` Claudius Heine
2019-02-14  3:53   ` [meta-eid] " kazuhiro3.hayashi
2019-02-14  6:19     ` Jan Kiszka
2019-02-14 10:18       ` kazuhiro3.hayashi
2019-02-14  9:07     ` Claudius Heine
2019-02-13 15:18 ` Henning Schild [this message]
2019-02-14  6:08   ` kazuhiro3.hayashi
2019-02-13 16:15 ` Jan Kiszka
2019-02-14 10:14   ` kazuhiro3.hayashi
2019-02-14  7:23 ` [meta-eid] " Baurzhan Ismagulov
2019-02-18  3:04 kazuhiro3.hayashi
2019-02-25 17:08 kazuhiro3.hayashi
2019-02-25 17:59 ` Henning Schild
2019-02-27  9:08 kazuhiro3.hayashi

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=20190213161859.24c4df54@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=kazuhiro3.hayashi@toshiba.co.jp \
    --cc=meta-eid@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