From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6657472919531159552 X-Received: by 2002:a1c:c3c5:: with SMTP id t188mr121179wmf.15.1550129027124; Wed, 13 Feb 2019 23:23:47 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:1b94:: with SMTP id b142ls201720wmb.8.canary-gmail; Wed, 13 Feb 2019 23:23:46 -0800 (PST) X-Google-Smtp-Source: AHgI3IYRsuhKuFbMg6kHlohBZh5ZVnxU12xxJuRU2M8ELhJ346E2sVpC0BbpYv0dOkoyYZ/FbJgw X-Received: by 2002:a1c:96c9:: with SMTP id y192mr132767wmd.20.1550129026709; Wed, 13 Feb 2019 23:23:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550129026; cv=none; d=google.com; s=arc-20160816; b=NlUuQnjZ+odNsJN2kcc3E9oe6HVKzLlEJk0MYf/zSb9LTnw0yN9o4+W7W9IO8Anf9U IR4LVBCfO+IF1C9Xv/rVLxN73py6cQvNsEsBkLma+vpuE0OjlVoi+8yYIAFjrOLMcLH9 Q9DJeb5zo2ardIoUuhRjofhprJ2NFjxzaVaFjlrQopJhDqD8ysli3Aih/d8ykqMB+JZ7 mxCwC37mb66vKmEjvRqVr3h4HKaJkKzR3Q+bstvv2oFlxAkY5/vKeHZSRWrWuk+pg2xr DLn6O1ht8KBfUkkcy5oxBzbmm+qR56qfigK/QZAK+qvPAN1ulCOM9qJD6SIoFfO3NK9w yXbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date; bh=pmmapA9YngYARjdFFEqnSGmrSmuLr6cZnNb8rOIus44=; b=SxsBOyhTbJK44jxli2ovtj+6cyDtscRnO/xZ6XfycksJ9bxRsyACkzum1VVzrSlH71 StXgpCCjEyDaJh3+lMMbHYvBElquCKKO8Epl7cOFbUSf0BBW5LxclyPu5yi6pWpdW6Zm GB/3zg6heSDYgyhOiMIxu8WPQUGT/+HcFdKy+D3/PPiMdE+el5L+5lUYOBaerxFv1ol9 9unmaez5+EDss1Yfe6RlzbEjT4OfciZHm0Wo6chB1ysmBK753gDLopBqFpS7U1YZM3wz P4sDbVCCMh4X4GbsCNuDhprlbCKJ4xz1TRnpeYi5WSNrWRHJhFSFuBC0pITSHBoSZ20l PsaQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id f6si444053wmj.0.2019.02.13.23.23.46 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 13 Feb 2019 23:23:46 -0800 (PST) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (dslb-084-058-239-227.084.058.pools.vodafone-ip.de [84.58.239.227]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x1E7Ni2M026660 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Feb 2019 08:23:45 +0100 Date: Thu, 14 Feb 2019 08:23:39 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Cc: wookey@wookware.org, meta-eid@googlegroups.com Subject: Re: [meta-eid] multistrap support Message-ID: <20190214072339.GP805@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com, wookey@wookware.org, meta-eid@googlegroups.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: aPUzAISbbcsl On Wed, Feb 13, 2019 at 01:14:57PM +0000, kazuhiro3.hayashi@toshiba.co.jp wrote: > 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. Neil told us that he doesn't maintain multistrap anymore. We also encountered issues (e.g., https://github.com/ilbers/isar/issues/16). For me personally, Perl is an obstacle (I go through Perl tutorials every couple of years :) ). So switching to debootstrap was easier at the time. That is not to say that debootstrap is the tool we want to have. The focus of debootstrap is to create Debian rootfss on Debian and non-Debian systems with the least possible dependencies. Given that, it is developed in shell, which is also not maintainable. In the long run, we'll need more and more introspection into apt & Co. for more advanced features. One way could be multistrap re-implementation in Python, as suggested by Wookey. ELBE has good experiences with libapt. aptly also promises some features we would like to use (though probably not multistrapping OOTB). Bootstrapping hybrid repos is also a useful use case. It can be achieved by making the "secondary" distribution upgradable from Debian, but if one has a lot of customized packages, using multistrap would require less effort and be less error-prone as well. In Isar, we try to stay away from massive modifications, but there are projects ending up tuning significant parts of Debian. The specific tools don't have to be mutually exclusive; Python offers enough polymorphism to include both as plugins (bitbake support has to be checked). With quite diverse requirements and opinions we already have today, we'll need pluggability, be it for multistrap or other features; the earlier we start playing with it, the better. For me, it is the question of enough itch rather than resources. For your specific use case, I don't see a problem using multistrap for meta-eid till we have a better alternative. With kind regards, Baurzhan.