From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6478538670852800512 X-Received: by 10.28.143.13 with SMTP id r13mr138721wmd.30.1508404373574; Thu, 19 Oct 2017 02:12:53 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.186.15 with SMTP id o15ls1833658wrg.13.gmail; Thu, 19 Oct 2017 02:12:53 -0700 (PDT) X-Google-Smtp-Source: ABhQp+TE7hBV5DRbZcUu6aTxHkEOeZER086OqKpTMd102b7ztOrACQYhflvq5BeG32+psMlTjNs1 X-Received: by 10.223.185.26 with SMTP id k26mr106883wrf.22.1508404373338; Thu, 19 Oct 2017 02:12:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508404373; cv=none; d=google.com; s=arc-20160816; b=epc4lNoloLAK7Y0j+Es0fjAIzjFJl73PWcHBMyfZzSx9E83aEUyD5p2m1yO4/H2YnH jeblIQXOKoRR+ZqXlgKDdp5JrDyDAe2UNFxwkBejgk/W7hJoTxkuCSdLLlHBSC0VjWj5 J4+eA0soZVDUBtHJhgVRW3t0ytz03u/cu4bBXIbY4qBaxdiCCr4Xj0fdWbAz7ugVwDKV OxnljN5HSyClWvCD7S/+Osw51m4wH8vPlehAbB1KG2ZhBnlHLGBwgu8U03ubpDKTQ3/j 26lo8bnRlauCetPvTaJm3Y6BmhOaG/67ioUoIJurvDgLNXkoymcOa/VDcblCzX0REXZJ KfRw== 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:to:from:date:arc-authentication-results; bh=syKQ37fc/Ka3FVxIP/bzl3eLoQ1ob/W9WTHeCXLZO50=; b=yBK2rpIAojqp7LsPkg9AdlZcQBQG9gKUuxnKtXOLS/uWPU2F37leYEbwlX1RcHZUGe D/ncLHrKkP7UDZFHkJ+AaXmCwJK3bD4wjuty2hxaBa+xvYKE3UtTFilmRT/6O4TUJqQv gDn6cmW+tOXzs7LXbUEv4tr/KCvGfnBeDhnxybbTKzVh/rIUp7tYPLACxLnPpEBTKMqI eSJVS+eimMAFH+1UeoSQtRENNBJ3DNxtBbMxGspHSHKEJFBykBdACPQ2b4ozQpKIXmhg a7JJSpDOZPJgUWnx3Fz2Vm0KRnkxLsVgmUeLgFWHBvTfuOAhl1v7RFZYYZdt4IScvV0v AOSw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id r15si859421wrc.1.2017.10.19.02.12.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Oct 2017 02:12:53 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id v9J9Cq0r017699 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 19 Oct 2017 11:12:52 +0200 Received: from md1em3qc ([139.25.68.40]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id v9J9Cqgb013622 for ; Thu, 19 Oct 2017 11:12:52 +0200 Date: Thu, 19 Oct 2017 11:12:52 +0200 From: Henning Schild To: isar-users Subject: Re: Introducing chroot tasks Message-ID: <20171019111252.53e26914@md1em3qc> In-Reply-To: References: 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: cvWJnt6OCz+F On Thu, 19 Oct 2017 01:38:48 -0700 '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}" /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 >