public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] Factor out meta-examples
Date: Wed, 24 Jan 2018 08:52:42 +0100	[thread overview]
Message-ID: <23ca38c7-3718-f70f-532f-697b7023d69c@siemens.com> (raw)
In-Reply-To: <eab9c7ae-35ed-12f7-0375-358d07bbed5f@ilbers.de>

On 2018-01-24 08:49, Alexander Smirnov wrote:
> Hi,
> 
> On 01/24/2018 10:34 AM, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> 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.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-01-24  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24  7:34 Jan Kiszka
2018-01-24  7:49 ` Alexander Smirnov
2018-01-24  7:52   ` Jan Kiszka [this message]
2018-01-24  7:56     ` Jan Kiszka
2018-01-24 10:04       ` Alexander Smirnov
2018-01-24 12:15         ` Jan Kiszka
2018-01-24 13:08           ` Baurzhan Ismagulov
2018-01-24 13:39             ` Jan Kiszka
2018-01-24 14:09               ` Baurzhan Ismagulov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23ca38c7-3718-f70f-532f-697b7023d69c@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox