From mboxrd@z Thu Jan  1 00:00:00 1970
X-GM-THRID: 6478538670852800512
Date: Thu, 19 Oct 2017 01:38:48 -0700 (PDT)
From: Ben Brenson <benbrenson89@googlemail.com>
To: isar-users <isar-users@googlegroups.com>
Message-Id: <e25b74e0-bb02-4b97-a2bf-c9da537a36aa@googlegroups.com>
Subject: Introducing chroot tasks
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1561_31117120.1508402328318"
X-Google-Token: EJjJoc8F2Mb_2yx_fPQ0
X-Google-IP: 178.27.65.121
X-TUID: PX7WK9Qg5Fte

------=_Part_1561_31117120.1508402328318
Content-Type: multipart/alternative; 
	boundary="----=_Part_1562_1482104749.1508402328319"

------=_Part_1562_1482104749.1508402328319
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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?


Regards,
Benedikt

------=_Part_1562_1482104749.1508402328319
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>I want to submit some patches for defining and =
running chroot tasks within bitbake recipes.<br>The following short example=
 should show what I mean:<br><br>Exampe recipe.bb:<br><br>do_foo() {<br>=C2=
=A0=C2=A0=C2=A0 # Do something within chroot<br>}<br>do_foo[chroot] =3D &qu=
ot;1&quot;<br>do_foo[id] =3D &quot;${BUILDCHROOT_ID}&quot;<br>addtask do_fo=
o after ... before ... <br><br><br>By setting the chroot flag the task auto=
matically will be executed within the chroot specified by the id flag.<br>M=
y isar (https://github.com/benbrenson/isar) fork already supports this feat=
ure, by using schroot.<br><br>This will give much more flexibility and modu=
larity to Isar. You will be able to append/prepend things to those tasks<br=
>between layers easily.<br><br>I have already seen, that there is another a=
nd better approach than schroot -&gt; proot.<br>I saw Alexander has already=
 experimented with this feature, which seems to work.<br><br>So before post=
ing some patches here, maybe changing this feature to proot first would a b=
etter first-step?<br><br><br>Regards,<br>Benedikt<br></div>
------=_Part_1562_1482104749.1508402328319--

------=_Part_1561_31117120.1508402328318--