From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6478538670852800512 X-Received: by 10.46.93.151 with SMTP id v23mr36323lje.12.1508404289560; Thu, 19 Oct 2017 02:11:29 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.20.8 with SMTP id u8ls937553ljd.9.gmail; Thu, 19 Oct 2017 02:11:29 -0700 (PDT) X-Google-Smtp-Source: ABhQp+Qdv1mS8mA9xQDI8eujtz+Darpkgsu2V46yC+qYVjX/Bxy6B08e8C1+EboFMG0BHRRWFawC X-Received: by 10.46.91.65 with SMTP id p62mr36382ljb.29.1508404289176; Thu, 19 Oct 2017 02:11:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508404289; cv=none; d=google.com; s=arc-20160816; b=MNrsPFPg7KLvyAb/CQPYk2QTNDqMr2D6Huv2qkfvWPzq41N2P+ZIvL1FRgCAWEKsk1 zTQLeHbUCys/7nfN3DqJkz9oujFrz/AZvENUDtibTVE7e7NxRs5g87IRzYJrAca355gr 0w9dppf3i/fdam00ho4sdV2q30m7KRenECzgPD2EAVBjc1EYnEX/LFkOt93bKVLdN4PD tAzNg2QKZ2gtabms9wq9JdH6IjJmeILOHue/8MGkOCunk/7ZwS0k2lucQ+22vfwpk9y9 zPTu9xntOJwdgLT2j6tLnbW8h/y72jhF8mF9ScFEBG3UwqLUxjOyGqICy7zJhCfvXq7z IfqQ== 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=tIfvVR/M+8nk21wkRGuph/vQEI9tKjoaPrqOdnOWUzbzkRiwKvlnFgAlfcipjm/n/r p7u9U+OMkKsfXjlOtqwB4LKAX7rnWDCT1YE9+qLrCFHwQWi4Mc/jZdGTQ8riWxeV8AWW O54XHxeCWDw4kd58jbXT4i95fuFr8yxxdDwCnBqQ6jiC64CnbzVeoSxifwCK0hL2SSud Ss4A2sKehb81FmsYTgjuqmofP/bvVujClYQtq0F6fG3sPERpmNzZg0kUxykGR56sPOnp ov5BzjPdK7INOZ4lBWLf4ITUB7sbcd7TKEYKrdRjaLFib4J0jpP4SoemIlLAiOVJ57h5 9o+g== 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 r17si744110ljb.2.2017.10.19.02.11.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Oct 2017 02:11:29 -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 v9J9BStP011653 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 19 Oct 2017 11:11:28 +0200 Received: from md1em3qc ([139.25.68.40]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id v9J9BSan004783 for ; Thu, 19 Oct 2017 11:11:28 +0200 Date: Thu, 19 Oct 2017 11:11:27 +0200 From: Henning Schild To: "'Ben Brenson' via isar-users" Subject: Re: Introducing chroot tasks Message-ID: <20171019111127.52fa61b3@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: nKZLuhtVN3x6 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 >