From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6478538670852800512 X-Received: by 10.28.230.79 with SMTP id d76mr130759wmh.12.1508404094472; Thu, 19 Oct 2017 02:08:14 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.11.143 with SMTP id 137ls1286394wml.0.canary-gmail; Thu, 19 Oct 2017 02:08:14 -0700 (PDT) X-Google-Smtp-Source: ABhQp+TIWMtysJUBGjnsJFroQqCfHrAvMuDhvybpPkNQXmJrCc7fxcMoIYi10LpysrsnfykPEslv X-Received: by 10.223.135.55 with SMTP id a52mr94513wra.28.1508404094202; Thu, 19 Oct 2017 02:08:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508404094; cv=none; d=google.com; s=arc-20160816; b=DkVuvDAO0PaFceOBtYtDGzRvPcGke5tGR+JMyCM/sUZoE+M2BVY08aT7omVIRUpVYK 5Vi2BtT6OM3blwEWQ+tO9pD+ZxyZ2cRsryM9y1FsiuBZfzzArhg64qZVltKZwLR7v73N oN1EDA6LYMj4QJ73hB6Y9NLjaKwMLF5q4ZaVWyzjwh5/ZlXdaxwot5n1MzkxQpVYY1MV NlKoNZNwtZ2P8KCj9uNq2TmkpqLW0kDOWyODp7awQiCXM+34u4eD7nRixniNtl231dR5 sNRuDoN8uBKgMauIpjsxPXX2zZA1SOYdU0ajlWWJTwN74O6rRMKTSlF8QYbDRMf1dWP6 l73w== 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:to:subject :arc-authentication-results; bh=NLR/IdsJArEItXnGJtyLHfV4bMq5QU2cjzbLdbLQ2FU=; b=aqNEfPGudAapAgF+KTyYFwyTAg14kqZIUJytXie0oPAUOTQV9j7Ga9JK3f5M30oN8Z qXeYfeKYv0wo5HukvDUknZdaMkLLm0Md99wyHJxmEJiMlI87lVu3SzDEUz75tn4YtL/I 7u13gVPS5mGXfIkIfPbCAAjrfjUJExShmEjpgzgpZ8oSBl9MKdWqxUTEpImVFX9YueRc 1Oc6hphkELw58nDw6AoOL70zLug1lwx6wLd9wZ3F3/GR59KPcaqoAjekxdmFf6sjLVRr Kq25j1R474dhcWdFt80nawNg6E8zML/LdjeHkE1sNXRDau/2GhsPo2N1RzEXZ/7WCCOa Y35w== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id e29si536568wrg.2.2017.10.19.02.08.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Oct 2017 02:08:14 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id v9J98DQv000874 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 19 Oct 2017 11:08:13 +0200 Received: from md1f2u6c.ww002.siemens.net ([158.92.8.28]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id v9J98Cns008342; Thu, 19 Oct 2017 11:08:13 +0200 Subject: Re: Introducing chroot tasks To: "[ext] Claudius Heine" , Ben Brenson , isar-users References: <81c9592a-74df-25d8-70ac-978f6ef1694e@siemens.com> From: Jan Kiszka Message-ID: Date: Thu, 19 Oct 2017 11:08:12 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <81c9592a-74df-25d8-70ac-978f6ef1694e@siemens.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: 65cW6xUQljc7 On 2017-10-19 11:01, [ext] Claudius Heine wrote: > Hi Ben, > > On 10/19/2017 10:38 AM, 'Ben Brenson' via isar-users wrote: >> Hi, >> >> I want to submit some patches for defining and running chroot tasks >> within >> bitbake recipes. >> The following short example should show what I mean: >> >> Exampe recipe.bb: >> >> do_foo() { >>      # Do something within chroot >> } >> do_foo[chroot] = "1" >> do_foo[id] = "${BUILDCHROOT_ID}" >> addtask do_foo after ... before ... >> >> >> By setting the chroot flag the task automatically will be executed within >> the chroot specified by the id flag. >> My isar (https://github.com/benbrenson/isar) fork already supports this >> feature, by using schroot. >> >> This will give much more flexibility and modularity to Isar. You will be >> able to append/prepend things to those tasks >> between layers easily. >> >> I have already seen, that there is another and better approach than >> schroot >> -> proot. >> I saw Alexander has already experimented with this feature, which >> seems to >> work. >> >> So before posting some patches here, maybe changing this feature to proot >> first would a better first-step? > > Yes. Since proot solves some more problems than schroot. > > Your implementation requires patching the bitbake code, so maybe we > should try to get those changes upstream to bitbake? > > Isar has currently has no own changes to upstream bitbake and I am not > in favor of forking bitbake. I think we should go for the most promising candidate of the chroot solutions for upstream and, if that fails, fall back to VMs. Whenn all our forces are joined on this topic now, we should be able to come to an answer quickly. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux