From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517546778931232768 X-Received: by 10.223.191.16 with SMTP id p16mr707803wrh.28.1517504600235; Thu, 01 Feb 2018 09:03:20 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.223.139.199 with SMTP id w7ls2554584wra.5.gmail; Thu, 01 Feb 2018 09:03:19 -0800 (PST) X-Google-Smtp-Source: AH8x225lGwsAiz5L41/9kRex696DN0zKbk+TLz0mObmjr6Tgj34fWbai3rlqaEwRQ8u9Q0jI78wU X-Received: by 10.28.192.4 with SMTP id q4mr3748097wmf.25.1517504599678; Thu, 01 Feb 2018 09:03:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517504599; cv=none; d=google.com; s=arc-20160816; b=ADF1EniTcbyKoaGJ9F2xUzEP42Mz0GFHkfnrzTPM57fU3MT+WNzCr+jEFmgqZUDvKi v1I6YU+A7BsjK9kEMGLJQr7gpGYyCBZjNy3PfizYsaqq20JeUzcinyZlSLslncHpNdWP SHFlcsMeP1G7pXVU9UMZHJiuW7anGs8QtXPIrNnq6Zf2cdc97PM9p3drQbCXTm39+69M 0lr8erKBxlTr3D+37B0HjmeHCBerOycXXcAZsamzMn+nr8wRVOyDl5ztRO1jZ/CPAZPv zIQdH4TqQb0VwMGC8q15xazVQDNgX+gH2cmLQkFNFB6522GvGSuKC70WKMj57lSZR2qR AKOA== 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=cfeGMIn6jStueS6kW4hUQuA5iBKEfIiZnxmGNGj/Edo=; b=JHVMA9Dr0urMDut4PaoP7vWrWOd9RT2kJ608FR0mg/8Vu5Thm8+IHyFAodubqxl8rr tcQNHLGCJ5/mGpf3/4MeAs8t6YoHZRIbL9ZnvtTympoycdNuz6cSTqd/R0zyt0tnLG1A g9Q35U88yZdyBSWqhy/ZHb/3VxXLQpS6zapcKWiPbBpLOqbRamy0WNnoy5GKHp4+b5Vs USxedGfGwTkhTHvXyr4Fd7r0gN1q1byRrHvFjMSHd9LXv760zU396rOYXBPrWg661nL5 uxIkdowboMIptC89tEd0v3bMDHoqJTLD42Zg0/C2VpzRMCjE85VxFJ8CJ0TZW/Pr/5ua Entg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id f6si155083wre.4.2018.02.01.09.03.19 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 09:03:19 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w11H3IDC004761 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Feb 2018 18:03:18 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w11H3IU2011308; Thu, 1 Feb 2018 18:03:18 +0100 Subject: Re: [PATCH 0/4] Rework isar-apt To: Alexander Smirnov , 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> From: Jan Kiszka Message-ID: <72ce4a2a-dd40-b53b-9134-7bb35ec443ca@siemens.com> Date: Thu, 1 Feb 2018 18:03:16 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: VNxzU2kAvLhI 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! > >> 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 > >> 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. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux