From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6657472919531159552 X-Received: by 2002:a1c:f718:: with SMTP id v24mr45342wmh.4.1550066171405; Wed, 13 Feb 2019 05:56:11 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:e452:: with SMTP id t18ls3989946wrm.3.gmail; Wed, 13 Feb 2019 05:56:10 -0800 (PST) X-Google-Smtp-Source: AHgI3IaroSFXUGrCJjbMZ23cilD2GI+yhpVr7Iv9sr6WDxyOXneLJa1VsiyR7zqMqJZBNbdHP6E9 X-Received: by 2002:adf:f9cc:: with SMTP id w12mr50115wrr.11.1550066170969; Wed, 13 Feb 2019 05:56:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550066170; cv=none; d=google.com; s=arc-20160816; b=MmYzB8/4gjQoyznAmLnDKXHKrEu53ZxsCdYu2JD+K1GgltjO8tx5bUQGXyEM3WNfUK WthqxPsHfpT1roDWGlcnVxAkuJzRoFfVXeNC6QJV4pBh5UC7Yh9D1r4eI+3lsT+gF1UI JxdTEI9hHPz9pzxs43HQdVSZFdJCGOiKCSPsAposFGHvryETitmgJVT51stXcpknv1rv IbW0Rs4s8b/Rg9cmgrci9RY1BLjfYLZ4HELzfAaUYKMfEVtNKdbv1MmBvwdVCfGzPaEV 9gcFk08+aqZClGztpohd7iMClvjjd0f6WzaqSkex3k9MhebjdXjWxwvYXvcXJYLvf7QS bs/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=RG1GU3dcCcnzviSJ9Bi/S2ApDY9nLChBj2QAzXPJ0sw=; b=DwQ9zaICnuLWnKNh+Cw8Yh8aEy8lf069uEFD52yO7puHj+95bgw4GEOGXbQ9Srpkmw gkAaSZt3dQhBawaCk3oqybngfstsW1UjhPy21GgbauBbiHfaXqjmeUVzPy3ds6r+1KzQ tgG1VLgUE5fJ0bZUJ5FWAZaKLvmiUicdO0HseBIOo5DAj8EpJZoSUdG/WJAid8j7r/89 FAB49YVKjqnzbSw4atX4cseheD9Ev6vip6gmoLnnHSC87D1irrdjTIF8wjBd/krwVBIZ oQkpamW7e90m+4jzLEya/4wgzMFtbVV5qmNlWiYh+Ei8UA6BaCx4ax8rapKIOvC9Qc5K XBtA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id t23si252993wmt.1.2019.02.13.05.56.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 05:56:10 -0800 (PST) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x1DDu9DN018118 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 13 Feb 2019 14:56:10 +0100 Received: from [139.25.69.181] (linux-ses-ext02.ppmd.siemens.net [139.25.69.181]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x1DDu8AJ027163; Wed, 13 Feb 2019 14:56:08 +0100 Subject: Re: multistrap support To: kazuhiro3.hayashi@toshiba.co.jp, isar-users@googlegroups.com Cc: meta-eid@googlegroups.com References: From: Claudius Heine Message-ID: Date: Wed, 13 Feb 2019 14:56:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: BwUFrG1m+MUk Hi Kazu, I don't speak for the whole Isar community, but just from my point of view. For context I implemented the switch from multistrap to debootstrap. On 13/02/2019 14.14, kazuhiro3.hayashi@toshiba.co.jp wrote: > 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. No, only debootstrap is supported and we will most probably stick with that. > 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? That is one of them. Debootstrap is better supported by the main Debian community than any other bootstrapping tools. And since it is out of scope or the Isar Project to implement its own bootstrapping mechanism, we will stick with the second most official one 'debootstrap'. The Debian installer being the most official way to install Debian, which is a bit to bulky and integrated to be easily used in a scripted environment. Both multistrap and debootstrap had or still have some inconveniences with our usage and it would of course be great to have one that fits exactly our purposes and is used and supported by the broader Debian/Embedded Debian and possible Debian server community. But as I said Isar does not have the resources to implement that. > (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. Maybe you can give an example about which feature you think could be moved outside of the isar project and be used separately. One issue here is that Isar uses bitbake as the build task scheduler, so shell scripts etc. are difficult to extract from it to be used outside of Isar. And if they are extracted from the Isar recipes, then using them in Isar again is disadvantageous for the Isar build process. So sharing code between a bitbake/isar project and other build systems is not really possible. regards, Claudius -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de