From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6617812835611181056 X-Received: by 2002:a17:906:6dc7:: with SMTP id j7-v6mr476164ejt.10.1541072604385; Thu, 01 Nov 2018 04:43:24 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:234c:: with SMTP id m12-v6ls2119381eja.8.gmail; Thu, 01 Nov 2018 04:43:23 -0700 (PDT) X-Google-Smtp-Source: AJdET5cmHyyGI2z3bzb7B59WYbJ7/aLVemwUbDRGOkj1NiOpSrTyvDtq4Y8bKJZ0zw5eOAukbb0j X-Received: by 2002:a17:906:6dc7:: with SMTP id j7-v6mr476162ejt.10.1541072603939; Thu, 01 Nov 2018 04:43:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541072603; cv=none; d=google.com; s=arc-20160816; b=M+mfaeszTlS9cGxvDZMHUirMgbDU+XVFzGp+oVpGlQk+gh9vCPd1uS13UyqKS0T0et YXh45XGVf4nSXM/V0VuZgxH5CVDUDZeMNkSa02B5dCTBATram8SnxlgARcgcnj6eBfiR Ek/zZ4EhxvF992Lh1LPSnCklbtTm9BTUg+2JZFphPl9YFQYjsidaD/v/E776WTmTVB5t f/STD/v1Co5t1g+3qb/13dQO35M/6Pi/gRU58Cx80R3cCC9uhDWkaExVYGHoSCTZXm2l 55ZvS/8W06JrJXJ/XuPQaVDZeX4Pr9aCpj3NWxLAI0aERCAGNh1V46Xc5EhaxOR65MLS s5ug== 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:organization:from:references:to:subject; bh=H0ShefGmL1AG/3Xx/UaJavZM/9aO1ed47umgdDFrouw=; b=Al1tDEa9WAL4QECbUh2UzY+aAOcCOimDsKJfjYTioo9tVtiY81edjtpOyg66kLl6dY AT1JviWfMcpUC7HzX4g+XwK5pb6+E7VxxcnTDR2owRh/8uAu8ZOWOsh6MVpdtdFPPGdI iqxS5wseupK3l8XBXQDOzlOJB8agZxOaFzo5KIHGluPbgd11/MorSaB/cyerzJBW/FVv qxSOcaXUCKruT23LI1huIAKSJXggh9lnKaHHV2gxwMFBXOhoioSJewby2XTBK287NGSg 0xUwGi0XflfthzCFDC8NAWJNYoLBpK0n8+/tS1pUHKPtocfg+cz78ZU5Ij1lgtxFl0x0 cMaQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of mosipov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=mosipov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id x43-v6si946614edd.4.2018.11.01.04.43.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Nov 2018 04:43:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of mosipov@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 mosipov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=mosipov@ilbers.de Received: from [192.168.50.180] (nat-ppp-217.71.235.199-satnet-spb.ru [217.71.235.199] (may be forged)) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id wA1BhKjV019178 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 1 Nov 2018 12:43:22 +0100 Subject: Re: [PATCH v2 0/2] introduce isar-image class To: chombourger@gmail.com, isar-users , Jan Kiszka References: <20181030134154.7adc8bf9@md1pvb1c.ad001.siemens.net> <20181031061025.28840-1-Cedric_Hombourger@mentor.com> <57847f7a-9b85-65ef-b11e-8952bf532e0f@siemens.com> From: "Maxim Yu. Osipov" Organization: ilbers GmbH Message-ID: <0af803c4-dce1-b872-37ea-00be7c1bf6ed@ilbers.de> Date: Thu, 1 Nov 2018 14:43:14 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: Q4XuXO8Aodjk On 10/31/18 9:51 AM, chombourger@gmail.com wrote: > > > On Wednesday, October 31, 2018 at 7:39:14 AM UTC+1, Jan Kiszka wrote: > > Before we move things in meta-isar around: I'd like to first of all > get rid of > the dependency on meta-isar for building typical images. Everything > that is not > of demonstration purpose (specific boards, example recipes etc.) > should go to > the core layer (meta). Therefore, we should not introduce further > generic > classes to meta-isar. > > > Hi Jan, > > That's great to know, I was wondering if we had some guidelines on what > should go to meta vs meta-isar > We will probably need to document this somewhere and introduce some > mechanisms to have our CI jobs check if isar/meta is buildable without > isar/meta-isar Definitely we need to discuss such meta-isar refactoring: 1) Should we keep under meta-isar only support for several reference boards with some board specific recipes (bsp related, demo apps etc)? So support for other third-party boards shipped as separate layer will not include meta-isar? 2) What can be incorporated into isar from one of the isar users - jailhouse-images? > In the short term, I can amend the patch series to move the class to > isar/meta > I believe we could also place isar-image-base there but leave > isar-image-debug in isar/meta-isar since the definition of a debug image > we have there appears to be just an example > What do you think? In my opinion, debug image is generic enough so it has to be kept together with isar-image-base. Thanks, Maxim. > Thanks > Cedric > > -- > You received this message because you are subscribed to the Google > Groups "isar-users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to isar-users+unsubscribe@googlegroups.com > . > To post to this group, send email to isar-users@googlegroups.com > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/isar-users/f1c6cbd0-fd05-4e6e-a77d-b5867f501ec3%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. -- Maxim Osipov ilbers GmbH Maria-Merian-Str. 8 85521 Ottobrunn Germany +49 (151) 6517 6917 mosipov@ilbers.de http://ilbers.de/ Commercial register Munich, HRB 214197 General Manager: Baurzhan Ismagulov