From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517546778931232768 X-Received: by 10.28.15.145 with SMTP id 139mr3752989wmp.27.1517517146286; Thu, 01 Feb 2018 12:32:26 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.31.200 with SMTP id f191ls2034wmf.5.canary-gmail; Thu, 01 Feb 2018 12:32:25 -0800 (PST) X-Google-Smtp-Source: AH8x226bA7YVOpZdVAsfV8jm20aXlPueVH5hL2zqW9RwSbFElaXQxn3QZ4NwEbLzRg2Rs3TIPecQ X-Received: by 10.223.182.4 with SMTP id f4mr4086259wre.32.1517517145749; Thu, 01 Feb 2018 12:32:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517517145; cv=none; d=google.com; s=arc-20160816; b=sQ8x3DoYV0Bl7gPWM6yKqrx/Fp5nFJ4qZ+MV1EC+jG/h5LyzDNzAI+UJjl8j2Mrv3g WnRl4sLQkKxyeFMUeRJLmkKKgpZosWhcbwoCZHymxYIwr6ciBNyZAW8C+bsgpcLNUI/x PJjLuOWw5xk3mQPhxFj94DfMIJtSggFz+5O7e48SikpYfDVQP1AxLJGZDbkF0Up2G4IX z8W3rQVF+EDWLodQt9DeD1LuuMnOOqZ93GWQy0h8DjlwbDfMiRFTmeOotut63vdsuGW7 1rPnZyZuX8V21Fyo1xfLpbMiBLbs2a+2y+iOoaLcYaKWpmEx8nVw1J2TDv+fBfoK9nle SqGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=lQWabUmVCjv0AamUqySdK426h+FfO+qB3Pbp/8PLKJc=; b=wNaPGn69vIVTh5GFIA9jrF3SCY9h/CgLzsd8AgWBrNiXgWEqzHJgYHgnpL8Vp0Q76y dDmNCJezW5qfZfDhGFkOXenW3616vr9tKyXlk4uv1SMdW/DFNOvxzF/5mZUt06H9q3FF KLoLCuFXlZtH1gPc8U5dQS7vV1v94ZRqq5xvIk1+RqRajt0bakork2+m2VoieiETrBFz Zk4gF2NlepvARiCRX6u657/av2dZi7dLpIuE+Y0cal7QcpDNeZ+F5S20HYwn7Qho4UyB gtwcErTaY5zA5WdPDDOAigjZNB/KNoHkhX8MqcIQy87U+NxBM228v2bdLI85FCTMcJjq ezdg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id a12si283876wmg.4.2018.02.01.12.32.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 12:32:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] ([188.227.110.165]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w11KWLTJ012913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 1 Feb 2018 21:32:23 +0100 Subject: Re: [PATCH 0/4] Rework isar-apt To: Jan Kiszka , isar-users@googlegroups.com, Claudius Heine References: <20180201112944.7877-1-asmirnov@ilbers.de> <360fe4b8-2594-0577-2859-dafd18d4c55b@siemens.com> <4fd7ef75-d180-af99-c6e7-ce5af9ab6a55@ilbers.de> <72ce4a2a-dd40-b53b-9134-7bb35ec443ca@siemens.com> From: Alexander Smirnov Message-ID: Date: Thu, 1 Feb 2018 23:32:16 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <72ce4a2a-dd40-b53b-9134-7bb35ec443ca@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: SSyxVj9788Vh On 02/01/2018 08:03 PM, Jan Kiszka wrote: > On 2018-02-01 17:54, Alexander Smirnov wrote: >> >> >> On 02/01/2018 07:25 PM, Jan Kiszka wrote: >>> On 2018-02-01 17:22, Alexander Smirnov wrote: >>>> On 02/01/2018 07:14 PM, Jan Kiszka wrote: >>>>> On 2018-02-01 12:29, Alexander Smirnov wrote: >>>>>> Hi all, >>>>>> >>>>>> this series intended to make buildchroot able to work with isar-apt. >>>>>> I've tried to add extended comments to each patch. >>>>>> >>>>>> Impact: with this series I'm able to build 'example-hello' <-> >>>>>> 'libhello' >>>>>> without any hacks. So the deps are installed automatically. >>>>>> >>>>>> NOTE: I've migrated to bitbake [lockfiles] mechanism, don't know how >>>>>> robust it >>>>>> is, but build in the loop started in the evening didn't fail during >>>>>> the night. >>>>>> >>>>> >>>>> I can happily report: It works as promised also for my use case >>>>> (jailhouse.bb -> linux-jailhouse.bb, both Isar-built). >>>>> >>>> >>>> Thanks! But I've found an issue with events. :-( Our bitbake didn't >>>> handle them for multiconfig, the following patch seems to add this: >>>> >>>> https://patchwork.openembedded.org/patch/141626/ >>>> >>>> Events is very good mechanism to clean up Isar build from pending mounts >>>> without headache with build fails, so I think it would be valuable to >>>> try latest bitbake. I'll report the results as soon as build finishes. >>> >> >> From the first like I like it: >> >>  - build output looks more user-friendly: >> 0: mc:qemui386-jessie:example-hello-0.2+7bf716d2-r0 do_build - 222s (pid >> 15637) >> >>  - Yes! Events are now handled by all instances, so no more pending >> mounts. :-) > > Even on ^C^C (forced termination)? That would be valuable! It seems so, I've tested several times by interrupting the build with double CTRL+C, isar-apt is being unmounted in 1-2 seconds for *all* multiconfigs. :-) So I definitely want this bitbake and add /proc, /dev to clean up hook. > >> >>> Perfect: Claudius just told me we need to update bitbake anyway to have >>> proper multiconfig support (i.e. no more hacky copying of files during >>> isar-init-build-env). Claudius, which version at least? >>> >> >> Hmm, didn't get what is "hacky copying"... > > That we only pick up an use multiconfig/ files from meta-isar, not any > other layer. See > https://groups.google.com/forum/#!msg/isar-users/IjQTuBFLPLo/IqRREtAHBgAJ > Ok. >> >>> BTW, why are we copying bitbake in? Wouldn't a submodule make more sense? >>> >> >> In my opinion not, the main idea is the same as for Yocto - have no >> external dependencies. Isar should be self-contained. > > That wouldn't change. You would still have both artifacts in the tree, > after checkout. And you could tar them both together for release > packaging. Or what are the concrete downsides? > > I'm not using submodules heavily, but here would be a good use case IMHO. > Have no experience in creation of submodules but sounds good, let me check this first in details, thanks for the idea! Alex