From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
"Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 2/2] meta: Set LAYERSERIES_* variables
Date: Wed, 14 Nov 2018 11:15:29 +0100 [thread overview]
Message-ID: <e710d9de-9aef-bef2-2167-d10e6b5940ee@siemens.com> (raw)
In-Reply-To: <20181114082047.22c98905@md1za8fc.ad001.siemens.net>
On 14.11.18 08:20, [ext] Henning Schild wrote:
> Hi,
>
> similar changes will have to be applied to custom layers. So an entry
> in RECIPE-API-CHANGELOG.md would be a good idea.
>
We definitely need better understanding here. I just played with the latest
version, and it now asks me to define LAYERSERIES_COMPAT_mylayer - so far, so
clear. Now I'm having already dependencies on latest and greatest Isar in my
layer so that I added
LAYERSERIES_COMPAT_mylayer = "v0.7"
to express that I actually need >v0.6. But that breaks the build:
ERROR: Layer mylayer is not compatible with the core layer which only supports
these series: v0.6 (layer is compatible with v0.7)
Should we have now
LAYERSERIES_CORENAMES = "v0.6 v0.7"
in Isar? Or something like
LAYERSERIES_CORENAMES = "v0.6 next"
?
Jan
> Henning
>
> Am Fri, 9 Nov 2018 09:59:03 +0100
> schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
>
>> Fix warnings after update to the latest bitbake.
>>
>> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
>> ---
>> meta-isar/conf/layer.conf | 1 +
>> meta/conf/layer.conf | 3 +++
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/meta-isar/conf/layer.conf b/meta-isar/conf/layer.conf
>> index 4aa1cf1..bc26516 100644
>> --- a/meta-isar/conf/layer.conf
>> +++ b/meta-isar/conf/layer.conf
>> @@ -14,6 +14,7 @@ BBFILE_PRIORITY_isar = "5"
>> # This should only be incremented on significant changes that will
>> # cause compatibility issues with other layers
>> LAYERVERSION_isar = "3"
>> +LAYERSERIES_COMPAT_isar = "v0.6"
>>
>> LAYERDIR_isar = "${LAYERDIR}"
>>
>> diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
>> index ab6ae8e..ec34d85 100644
>> --- a/meta/conf/layer.conf
>> +++ b/meta/conf/layer.conf
>> @@ -11,8 +11,11 @@ BBFILE_COLLECTIONS += "core"
>> BBFILE_PATTERN_core = "^${LAYERDIR}/"
>> BBFILE_PRIORITY_core = "5"
>>
>> +LAYERSERIES_CORENAMES = "v0.6"
>> +
>> # This should only be incremented on significant changes that will
>> # cause compatibility issues with other layers
>> LAYERVERSION_core = "1"
>> +LAYERSERIES_COMPAT_core = "v0.6"
>>
>> LAYERDIR_core = "${LAYERDIR}"
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-14 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 8:59 [PATCH v2 0/2] Update to the latest bitbake release Maxim Yu. Osipov
2018-11-09 8:59 ` [PATCH v2 1/2] bitbake: Update to the release 1.40.0 Maxim Yu. Osipov
2018-11-19 7:46 ` Jan Kiszka
2018-11-21 8:30 ` Jan Kiszka
2018-11-09 8:59 ` [PATCH v2 2/2] meta: Set LAYERSERIES_* variables Maxim Yu. Osipov
2018-11-12 9:20 ` Henning Schild
2018-11-14 7:20 ` Henning Schild
2018-11-14 10:15 ` Jan Kiszka [this message]
2018-11-14 10:39 ` Maxim Yu. Osipov
2018-11-12 9:28 ` [PATCH v2 0/2] Update to the latest bitbake release Maxim Yu. Osipov
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=e710d9de-9aef-bef2-2167-d10e6b5940ee@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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