From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6478538670852800512 X-Received: by 10.28.63.86 with SMTP id m83mr140158wma.21.1508404501950; Thu, 19 Oct 2017 02:15:01 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.157.208 with SMTP id q16ls1866656wre.6.gmail; Thu, 19 Oct 2017 02:15:01 -0700 (PDT) X-Google-Smtp-Source: ABhQp+RUWqG+Zrxsw7KgQ42qz54F3xhQ0TNPbxVqubXp8JhRNZOGkETlRGsFIWW9fbT/I1vp5PX4 X-Received: by 10.223.135.55 with SMTP id a52mr96372wra.28.1508404501724; Thu, 19 Oct 2017 02:15:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508404501; cv=none; d=google.com; s=arc-20160816; b=U1Grj77XC5EE/bzIGuecKBI9DC/xoVikvBBdMHsxFCgiN2UikPQ2sK1NC+nqeGwlqC Q4uwkgII9/oX7aM6MumyqA2ZU26OyYdgExM3UfItfde5uwNL562ouwsF1gTfcEYUNLsj dZcHqIwd9tSIvWrTlwDYTg8ywd84By3PSaFeEpggD9v3Zu8DE9D7ZFiWg2Bbh2V9M4fm EPbOftRCqcjOrAh2d4vXKx2U82gGoTgVXsLYvo6DblUXXoYwXUpJq4msIyB/+Es4iNMZ mrz0vmogsRehr1rYwIF5A535484C1z5q1q6tLBSxx/AvI7+7EtcElcC3A3p5+6ufnpHd DASQ== 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:arc-authentication-results; bh=SxdEw0pRMfGQ5IIkjIPquWiHWyxGvMuHOcB/yuB1k8k=; b=fD/SiP8D50rZ8FHQLf2EOt2Fdg5ftuDrq8oh9E3/Gf2GOD4Xpts5Qs0dOJXS6Jei9m bGo0MIzTtOsTppaxyJ0S8fiNrVeBteL8kmu7KiqHX9xFSyOzWLfFT/oumPkOE8qFgjHz afjbOZ7wCzhm5ru7D4eksyBGhR/UnQnrhtHBQWUcNgRC9hEMuURE0a4jocEj8JIUfHls 0mDv1tXdMMts9NvgapWk2dA454YtITDTJA7shIpIZ5qcYQQ7eHyFoLu1pxRlr2UZaVr1 VIoJToziIjWluBv7pU4LiqGWAAVAFYWte4pyZjAym0qjYjMvCFzV47qRYg+2nHX8SI6G 0GOQ== 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 l9si757562wrf.4.2017.10.19.02.15.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Oct 2017 02:15:01 -0700 (PDT) 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 mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id v9J9F0Mv013863 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 19 Oct 2017 11:15:00 +0200 Received: from md1em3qc ([139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id v9J9F0WY009491; Thu, 19 Oct 2017 11:15:00 +0200 Date: Thu, 19 Oct 2017 11:15:00 +0200 From: Henning Schild To: "[ext] Claudius Heine" Cc: Ben Brenson , isar-users Subject: Re: Introducing chroot tasks Message-ID: <20171019111500.44f150f0@md1em3qc> In-Reply-To: <81c9592a-74df-25d8-70ac-978f6ef1694e@siemens.com> References: <81c9592a-74df-25d8-70ac-978f6ef1694e@siemens.com> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: sGB9Eb/RTPig On Thu, 19 Oct 2017 11:01:28 +0200 "[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? IMHO, touching our copy of bitbake is an absolute NoGo! Such changes need to go upstream first. Henning > Isar has currently has no own changes to upstream bitbake and I am > not in favor of forking bitbake. > > Claudius >