Re: Introducing chroot tasks

[Henning Schild <henning.schild@siemens.com>]

On Thu, 19 Oct 2017 01:38:48 -0700
'Ben Brenson' via isar-users <isar-users@googlegroups.com> 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}"

/id/chrootdir/ ?

> 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.

One key feature i see here would be automatic cleanup if things go
wrong. At the moment we still have the case where umounts will not get
executed if tasks fail.

> 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?

You should talk to Alex before duplicating work. He is mostly
interested in getting rid of sudo, while your focus is a different one.
But you will have to touch the same code which suggests to serialize
the work.

Maybe you have other features in your fork that you can present before
the chroot-feature?

Henning

> 
> Regards,
> Benedikt
>