public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Ben Brenson <benbrenson89@googlemail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Introducing chroot tasks
Date: Thu, 19 Oct 2017 01:38:48 -0700 (PDT)	[thread overview]
Message-ID: <e25b74e0-bb02-4b97-a2bf-c9da537a36aa@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 1091 bytes --]

             reply	other threads:[~2017-10-19  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19  8:38 Ben Brenson [this message]
2017-10-19  9:01 ` Claudius Heine
2017-10-19  9:08   ` Jan Kiszka
2017-10-19  9:15   ` Henning Schild
2017-10-19 10:24     ` Ben Brenson
2017-10-19 12:00       ` Claudius Heine
2017-10-20  8:51         ` Ben Brenson
2017-10-19  9:11 ` Henning Schild
2017-10-19  9:12 ` Henning Schild
2017-10-25  7:49 Benedikt Niedermayr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e25b74e0-bb02-4b97-a2bf-c9da537a36aa@googlegroups.com \
    --to=benbrenson89@googlemail.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox