From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6478538670852800512 X-Received: by 10.28.32.17 with SMTP id g17mr112711wmg.8.1508403689386; Thu, 19 Oct 2017 02:01:29 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.47.194 with SMTP id v185ls1284228wmv.9.canary-gmail; Thu, 19 Oct 2017 02:01:29 -0700 (PDT) X-Google-Smtp-Source: ABhQp+Q1dSlVPwq03boQN2WM5m5AeagThy/CsEbpQpErj3IeEIWIJAnMXNCLT9ZHLXh3eNM6dfyh X-Received: by 10.223.157.136 with SMTP id p8mr101937wre.14.1508403689077; Thu, 19 Oct 2017 02:01:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508403688; cv=none; d=google.com; s=arc-20160816; b=VVG5R0zyms5MT7dk/OqWPh+zMdadvHr13+CHM15rMYJ8lneMvflDx82v5mbvoZv3Wx HWIWaC0fUT+DH3llGfgI1az7PR7ajnYvFsJHKkHFK4IVpLbZ0vVa9ZB7Yi6Dre9+B8Nm wdl2Qk30Rb9JRjE0sE+PRntlMlU39mFVBrbGKLa9ySuMBA+bd8M97kVUsUrO4tzRvcqO FibTXWG0YDnGIzqbZe4e3lR0z8gpI1YcsTzbAdvBhbjtyvrsPn6JJKPhugcEEdl16mbC OtDxZRaAhYhyrMIIHuCK+sE2ioRFlIhgP42yyAXkzNVIXRcaQSBIGoVJDxMhSH5Wz5Mm 7yBw== 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=CfJLNP0EM3vpkKFgWEb8PznwDd2zzIpUl5YXn5v0JSo=; b=hzlXBmXbLpmkT9ilYGj0ixRVdtfXaM0iVrvE3yi/O+LeO/JccsbsXT4wcKtPvTdyGL UfSauhSnBFWicJSWHHV5TxNFTz5dh+FkhjdCewOLV0yFJ6w1SiD/JthuRrBWovQoN5Ry +1/Mypmp0uzCjHX9U9tp6Cjah/kaJBfZW9FzxRX+2Eid1UbgQGT+LcWM3IquHKzBtbBj AxtofWbyYBiLG0PKnb8ZUMpFnLIDbXin1WSnrbsVcgEpIHtbwhNJRfbKVYSdAOLP0EGI 7jFKvX9oTvDqIR+VPaaX6aO+fMXAwZGDBSMuOO2vNHcTsGXaajmmuJ27lS1b5pUZ2jJK dteQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id e29si535185wrg.2.2017.10.19.02.01.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Oct 2017 02:01:28 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id v9J91SoV005358 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 19 Oct 2017 11:01:28 +0200 Received: from [139.25.68.223] (linux-ses-ext02.ppmd.siemens.net [139.25.68.223]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id v9J91Svd005441; Thu, 19 Oct 2017 11:01:28 +0200 Subject: Re: Introducing chroot tasks To: Ben Brenson , isar-users References: From: Claudius Heine Message-ID: <81c9592a-74df-25d8-70ac-978f6ef1694e@siemens.com> Date: Thu, 19 Oct 2017 11:01:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.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: F9EZWnTcLWpS 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. 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