From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6514517411576676352 X-Received: by 10.80.171.15 with SMTP id s15mr3461353edc.6.1516788256502; Wed, 24 Jan 2018 02:04:16 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.185.67 with SMTP id m61ls5007130ede.4.gmail; Wed, 24 Jan 2018 02:04:15 -0800 (PST) X-Google-Smtp-Source: AH8x2278vnNEzyHKLBD0KQ0HS1z/686GyvyC2WbX7zQWUvw3rDG55BtLIL4h9l5n/2/t47C7zX2U X-Received: by 10.80.204.74 with SMTP id n10mr5281032edi.12.1516788255784; Wed, 24 Jan 2018 02:04:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516788255; cv=none; d=google.com; s=arc-20160816; b=FW+yoADQC1hywaXxc3SvcwMZleIGdNWEymR2T6f1/PgzlInSjAviQg8CEED70ojpmX 2ldPKf4qOoLyUmS4+LLyFFto6H28v+rqnp7kpujnmorkP9bNTawOzoccl57rsYYRGci9 GOEXJ2OUGJCv2lsXbsKWAtC3ty8gNDG9emRizn3Yn+02qBdmBuSVFoAMpNjg6s2oPDK0 ZZmoOSV1/jEOl6xBtKJSrP2KIrDJktQAc8Sc4k4cDf66xxESXc69Gb8Vy0IkZ1jn6JJD 0ZISQhJuASov9aWztwn7NuMVL+MHiHULJfWZ2bAUv5AY4rwtnvJlWYRdtd9ZkSd4nLEh 26NQ== 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=78eXPDjok0HZID2xHx2dChjsMrxeS3RV/njLuXXSSWA=; b=cq80Y5/s3zAePFQ122QDcn6rkuMOlGpyGRzRM7DTb3YS51NAtVV1345aO9P7UGBgpB yovYkrc+Am/jTZ1vgRlGI+CHOKQqZbXin2SL7z22unhg/ucM3my8apwdlIHC4setHx7Y NWn1+7VTtMtcqIlm/s/isLzajIFexY4QhiTKLSgsqsfIRm/fOnyQcqs5cXya+S1eFKK3 wHeahHYo8wyuw53SegjpkJzXI1LMWuToiUA+s5rLctXdkYliw/vmKUJ4QLmSHv4lP4H2 WD5oYtb6mRNAuL8qvSCKVUFDf/Q1kDqwV8qfd/C4KuJr16rQz/OBruFA0HzHqHLzEWdN 65ig== 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 g45si2909728eda.0.2018.01.24.02.04.15 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jan 2018 02:04:15 -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 w0OA4CNh016790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 24 Jan 2018 11:04:14 +0100 Subject: Re: [PATCH] Factor out meta-examples To: Jan Kiszka , isar-users References: <23ca38c7-3718-f70f-532f-697b7023d69c@siemens.com> <6780b230-1481-8767-89a4-129be64d4319@siemens.com> From: Alexander Smirnov Message-ID: <9fa572d2-8a59-b3b3-ab96-451975c72235@ilbers.de> Date: Wed, 24 Jan 2018 13:04:07 +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: <6780b230-1481-8767-89a4-129be64d4319@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: K2Qa33v+GSoz On 01/24/2018 10:56 AM, Jan Kiszka wrote: > On 2018-01-24 08:52, Jan Kiszka wrote: >> On 2018-01-24 08:49, Alexander Smirnov wrote: >>> Hi, >>> >>> On 01/24/2018 10:34 AM, Jan Kiszka wrote: >>>> From: Jan Kiszka >>>> >>>> Move recipes that have exemplary character (currently everything under >>>> recipes-app) into a separate layer that can easily be dropped when >>>> building real images. This also helps to ensure that no assumptions >>>> about customizations and core recipes sharing the same layer sneak in >>>> again. >>>> >>>> The meta-isar layer is still not completely clean as we keep >>>> bblayers.conf.sample and local.conf.sample prepared for building example >>>> images. >>>> >>> >>> Isar core is in 'meta' layer. Current 'meta-isar' is the example itself, >>> it's not intended to be used in real projects, it's a kind of template >>> for your 'meta-product'. >> >> This is the old view, it's no longer correct. meta-isar has become >> already a core layer that products build upon. We need to fix this now. > > BTW, we should eventually discuss the folding of meta and meta-isar or a > clarification what should go where. For now, I will be add the reusable > recipes for custom kernel builds into meta-isar, but it's not really > intuitive yet. > > We definitely must stop proposing users to fork isar in order to build > own images. That is a completely obsolete and counterproductive pattern. > As I see this patch is just a small step to new direction, but I have no idea what this direction is itself, it wasn't discussed here. Could you please describe the vision you assume to see finally? What is Isar core, what is example? BTW, below is my assumption what could be reasonable regarding Isar future layout: 1. 'meta' contains: - Isar classes - buildchroot - caching/reproducibility core; 2. meta-isar contains: - distro: debian-wheezy, debian-jessie, debian-stretch - machine: qemuarm, qemuamd64, qemui386 - images: isar-image-base (minimal multirstap image) - No local.conf, bblayers.conf etc... 3. meta-isar-example: - distro: raspbian-jessie - machine: rpi - images: isar-image-example - apps: hello, example-raw - local.conf, bblayers.conf etc... With this layout I assume that: 1. Debian is the reference Isar distro and it's included to Isar core by default. 2. Debian will be the most popular distro for customer projects. 3. To create new product, the user needs to create meta-prodcut with: - local.conf, bblayers.conf - isar-image-base.bbappend with custom packages set This layout will help to hide back-end magic like multistrap from user. So if, for example, we will switch from multistrap to debootstrap, 'meta-product' will work as it is. Alex