From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6478538670852800512 X-Received: by 10.99.185.86 with SMTP id v22mr159820pgo.76.1508408661215; Thu, 19 Oct 2017 03:24:21 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.99.121.205 with SMTP id u196ls1614469pgc.19.gmail; Thu, 19 Oct 2017 03:24:20 -0700 (PDT) X-Received: by 10.84.234.140 with SMTP id n12mr169674plk.5.1508408660836; Thu, 19 Oct 2017 03:24:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508408660; cv=none; d=google.com; s=arc-20160816; b=ew85xtHTRZ/0+ve2OpFFUVfO9d6LszhEY7y0otteAryKo7BCi0sVutDZuhDVuKIiTH 14cLMjvbsidUNJ5Igfmyc5sHM6OATKSb1GXkVBnZ1Wm+Vv4okxd2yLgOj28+4uxRXcvu 706pJ56KNPM0LZ3NxNYNX7DS1VXRGXXjcSO50trCVLx5rkl+L9Ch+AZkGaASI+eU9p/O LGtfTQhV5wWYUqohhEJ0wJgW8SVaxkMXYzBFbbikFcqR7O5bNLbG41T5OsyiElb01rZ9 nmZFueSJpvHBITyAaEMMrItugLSNdTRV/VrWFVFue3o0CXOiWFd5jwG4CLWy2Tcl9Qm5 MxJw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:dkim-signature:arc-authentication-results; bh=beaQP3dlbW8IRJaZXzw3yxsWkSMnJ2PuzrKhGGsFKsU=; b=fauBc5xJS87GMCFIFisEq1i4gdK1mpZb2CkZzvTFrFuko2S1Gjv3/+WfVWdmPVFmvR if08QGf9iZ/1nCwFb5ybshhm1B2VW06zphyjWd0gGOqcqpfbBCSkiOi44NzFso36EgXT llKq2uSEKVCdKscHa+0ODBTHwfPuafPJ246q7OGUQKQkg9TI4hKnqRME5+HC0jo8qttK o8cADeiRFgTjsl1OnJ4EXnI4Id1Dddo3TP8bvLlhL9Jv5yDnjvgS0o75M1+iLe8Zzyv4 BPlDMFGoEj6aCJ73Y4zViiqKo0q3CK5gk0Pjq1bT88yMNVazqn4Owlm+BHck44qBa4UW QEcQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=CyPcWamV; spf=pass (google.com: domain of benbrenson89@googlemail.com designates 2607:f8b0:400d:c09::234 as permitted sender) smtp.mailfrom=benbrenson89@googlemail.com; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Return-Path: Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com. [2607:f8b0:400d:c09::234]) by gmr-mx.google.com with ESMTPS id z2si860625plk.4.2017.10.19.03.24.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Oct 2017 03:24:20 -0700 (PDT) Received-SPF: pass (google.com: domain of benbrenson89@googlemail.com designates 2607:f8b0:400d:c09::234 as permitted sender) client-ip=2607:f8b0:400d:c09::234; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=CyPcWamV; spf=pass (google.com: domain of benbrenson89@googlemail.com designates 2607:f8b0:400d:c09::234 as permitted sender) smtp.mailfrom=benbrenson89@googlemail.com; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Received: by mail-qk0-x234.google.com with SMTP id k123so9705322qke.3 for ; Thu, 19 Oct 2017 03:24:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=beaQP3dlbW8IRJaZXzw3yxsWkSMnJ2PuzrKhGGsFKsU=; b=CyPcWamVZ61FRiWUP08cRImNVUCExHtyrReMU/JDh20URljI3IeBbkBi7oovTj63Vu FjfE9XL7n/LbjXm0JwrHdD9NXbVIxaj6HtDKGioiG8u/ASTCPdkcwMi7rHOe9VeGObdN IZJp5+3FOZX8uMEDkUBbr0DtUNEv/qE7Zm/pAtyHoF88qT5oGNHJvqfwIOP6WQUZYFaM tGQhOZDW52MOtVm3hZjf5TAmwsCPk1TETSSC5imVg450SbMoUqXXhmHs3Orktxt4Gake E9l5kyqCotAKogAewK40OBHGtD8Ykr33F8MJOwQs20cCMISPl0px0Tvd0AZnZJrL43kY otqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=beaQP3dlbW8IRJaZXzw3yxsWkSMnJ2PuzrKhGGsFKsU=; b=DDBDQcu03Tggzmrxq6MHsY4guue2HkaA4CuRbMEPxN6JIqH7RYKhl59o9+Zt6TUcay 5VjFYWN5loR0+ccy5dBjmTdVwktD5mSG1o+eEH9SwG7rwi53nFD54X09t9WEKxuhg/dr naoQVqKtAb4q4gn9+yCxmz+OvTeRPp09K+EhvvYJpmPCF2jIvBfY0mpZGXl36xDHepqW HQBlaTOHnWIdfeXUq+K//6EqRX2ihpkXFm+5wJ1Nyezxg9BMjqd4PLv4k+M3OV4Heej7 N4Fe4lZxjautFf5aeOkQ3Zg6iYopx4vPQLVu6p1ncKQC7i6xBCBVde9Oy2oz3X9xlHUv OzPQ== X-Gm-Message-State: AMCzsaWL2izmABdLa2B7YDqFQizLJ3DlNZ3Kis/kwaBJWD9nIeQHq4QO WOth9bco4GmgLA5t0DXfid/jz5hG9liPYsLZsrfefvUL X-Google-Smtp-Source: ABhQp+S3cBz5XoeuZ7G75P2rG/cSDwrICGEVLn+qd0h02mKA8lMoCww3Ex8nnWqulaoaYteDLqk/sJDlp9rbZhRRvno= X-Received: by 10.55.168.209 with SMTP id r200mr1228304qke.217.1508408660063; Thu, 19 Oct 2017 03:24:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.135.81 with HTTP; Thu, 19 Oct 2017 03:24:19 -0700 (PDT) In-Reply-To: <20171019111500.44f150f0@md1em3qc> References: <81c9592a-74df-25d8-70ac-978f6ef1694e@siemens.com> <20171019111500.44f150f0@md1em3qc> From: Ben Brenson Date: Thu, 19 Oct 2017 12:24:19 +0200 Message-ID: Subject: Re: Introducing chroot tasks To: Henning Schild Cc: "[ext] Claudius Heine" , isar-users Content-Type: multipart/alternative; boundary="001a114fce3e5bfad7055be3c2b7" X-TUID: Au7qG8E7XgnC --001a114fce3e5bfad7055be3c2b7 Content-Type: text/plain; charset="UTF-8" Yeah I know, but using chroot tasks was never a use case for bitbake and maybe will never be, I think. I've never thought about using chroot tasks when running Yocto builds, but that has changed very fast when switching to Isar. So maybe within Isar we have a more reasoned use case for chroot tasks, and if this feature works in isar, may be I have more chances to get those changes upstream to bitbake? I can try to get those changes upstream first.... Regards, Benedikt 2017-10-19 11:15 GMT+02:00 Henning Schild : > 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 > > > > --001a114fce3e5bfad7055be3c2b7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yeah I know, but using chroot tasks was never a use c= ase for bitbake and maybe will never be, I think.
I've never = thought about using chroot tasks when running Yocto builds, but that has ch= anged very fast when switching to Isar.
So maybe within Isar we h= ave a more reaso= ned use case for chroot tasks, and if this feature works in isar, may be I = have more chances to get those
changes upstream to bitbake?

I can try to get those changes upstream first....
Regards,
Benedikt


<= /div>



2017-10-19 11:15 GMT+02:00 Henning Schild <henning.schild@siemens.com>:
On Thu, 19 Oct 2017 11:01:28 +0= 200
"[ext] Claudius Heine" <claudius.heine.ext@siemens.com> 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 tas= ks
> > within bitbake recipes.
> > The following short example should show what I mean:
> >
> > Exampe recipe.bb:
> >
> > do_foo() {
> >=C2=A0 =C2=A0 =C2=A0 # Do something within chroot
> > }
> > do_foo[chroot] =3D "1"
> > do_foo[id] =3D "${BUILDCHROOT_ID}"
> > addtask do_foo after ... before ...
> >
> >
> > By setting the chroot flag the task automatically will be execute= d
> > within the chroot specified by the id flag.
> > My isar (https://github.com/benbrenson/isar) fo= rk already supports
> > this feature, by using schroot.
> >
> > This will give much more flexibility and modularity to Isar. You<= br> > > will be able to append/prepend things to those tasks
> > between layers easily.
> >
> > I have already seen, that there is another and better approach th= an
> > 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 ch= anges
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
>


--001a114fce3e5bfad7055be3c2b7--