From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
"[ext] Henning Schild" <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 2/2] meta: Set LAYERSERIES_* variables
Date: Wed, 14 Nov 2018 13:39:20 +0300 [thread overview]
Message-ID: <ee9ca817-826e-ed48-0cc9-da553b119ab3@ilbers.de> (raw)
In-Reply-To: <e710d9de-9aef-bef2-2167-d10e6b5940ee@siemens.com>
On 11/14/18 1:15 PM, Jan Kiszka wrote:
> 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"
>
> ?
Well... v.07 doesn't yet exist, but we have to express the fact that we
are on the latest tree (similar to Debian's 'sid' DISTRO_NAME).
I vote for the 'next'.
I'll prepare the patch together with description in
RECIPE-API-CHANGELOG.md as Henning suggested in previous email.
Regards,
Maxim.
FYI:
Latest reference manual
(https://www.yoctoproject.org/docs/2.5.1/ref-manual/ref-manual.html#var-LAYERSERIES_COMPAT).
defines LAYERSERIES_COMPAT:
<<<
Lists the versions of the OpenEmbedded-Core for which a layer is
compatible. Using the LAYERSERIES_COMPAT variable allows the layer
maintainer to indicate which combinations of the layer and OE-Core can
be expected to work. The variable gives the system a way to detect when
a layer has not been tested with new releases of OE-Core (e.g. the layer
is not maintained).
To specify the OE-Core versions for which a layer is compatible, use
this variable in your layer's conf/layer.conf configuration file. For
the list, use the Yocto Project Release Name (e.g. sumo). To specify
multiple OE-Core versions for the layer, use a space-separated list:
LAYERSERIES_COMPAT_layer_root_name = "sumo rocko"
Note
Setting LAYERSERIES_COMPAT is required by the Yocto Project Compatible
version 2 standard. The OpenEmbedded build system produces a warning if
the variable is not set for any given layer.
See the "Creating Your Own Layer" section in the Yocto Project
Development Tasks Manual.
>>>>
> 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}"
>>
>
--
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
next prev parent reply other threads:[~2018-11-14 10:39 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
2018-11-14 10:39 ` Maxim Yu. Osipov [this message]
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=ee9ca817-826e-ed48-0cc9-da553b119ab3@ilbers.de \
--to=mosipov@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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