From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6657472919531159552 X-Received: by 2002:a1c:28c4:: with SMTP id o187mr78934wmo.7.1550071141923; Wed, 13 Feb 2019 07:19:01 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:6b4e:: with SMTP id x14ls4057192wrw.12.gmail; Wed, 13 Feb 2019 07:19:01 -0800 (PST) X-Google-Smtp-Source: AHgI3IY1RI2hohibmntSZNx5a5cRKpJ/NcH4SxBT+Ams0M82gpdbsOb5OgoUrcQ1plK+HeyO8YLD X-Received: by 2002:adf:9e4c:: with SMTP id v12mr81645wre.12.1550071141479; Wed, 13 Feb 2019 07:19:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550071141; cv=none; d=google.com; s=arc-20160816; b=oMvhncf7Bs9AGXkQb00gTgeCuO1zQ0qv8GtixPNUVNg2Lleh7Isb/rpIgZIrm88oI5 K8HCp5ozRhNi8sFp9RiYuEB/3NosidxHYDsQU6YmsuJS0S2G1CpfOPIXQcrlm1fT8QMe 1zcDaSQtHKV/a3xK9lKCNmzAbFfWHsE0k5ZcOgklWlrIG1R/yje3hbB8O/ush/QJgha9 2RdCeexzZBt/J6xlTq7D4hddypwdf1T0s9A6Z07xWAFJnK+meRVfBqCRWaKPQHihGVq8 j7mctb1mCX2XHsOm7qj0Pe+l6/IY74DSFnjVCcs1pNkEwDtEgrwHYiCEmKGuA7aj3iJe 9toQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=K5AHD+9LmJJpHfXphRfVE2QR91TkmlFogs6hy24YQGI=; b=ZUzB8psefXqdsJHGpejy/6Xu4J+j5ftBXZ/P/pr2hnXP/CR509jBZYz9zuKASwqK/T PT4quApNwU0/lRHXq/FVtqc7NKFKC3ck5HVERArzJmZkjkdacszPcqJ9aKXZ5anEXEZ/ uymxSOKtmmjEdkZRcaFoua5/1H4lSQq4ucgaGvsbtX8jzsQj3+6XNYGSy/xvttjObUXN Y0aNoHMN/vspcrg89z6imsV7SI8rWrIKu5RXUB6a9zwCD79NCEmwAzH4QIYm2jlWN2aq /X3fYc/vasom76qkqq5W3yIMiIozV9dra1E09/xpOzSYxWKu5lNO47I2qyPoiRLGfTo8 ZwMQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id 109si67623wrb.0.2019.02.13.07.19.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 07:19:01 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x1DFJ0MZ021671 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 13 Feb 2019 16:19:00 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.0.97]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x1DFIxaH019684; Wed, 13 Feb 2019 16:19:00 +0100 Date: Wed, 13 Feb 2019 16:18:59 +0100 From: Henning Schild To: Cc: , Subject: Re: multistrap support Message-ID: <20190213161859.24c4df54@md1za8fc.ad001.siemens.net> In-Reply-To: References: X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: i/4QnOrb6rMy 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 -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 : > 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 > >