public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 2/2] meta: Set LAYERSERIES_* variables
Date: Mon, 12 Nov 2018 10:20:06 +0100	[thread overview]
Message-ID: <20181112102006.6f52306a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20181109085903.8299-3-mosipov@ilbers.de>

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"

Will this cause warnings or confusion once we are at > 0.6? Say i have
a layer that truly needs >=0.8 but sits on an Isar with the 0.6 still
in there.

Henning

>  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}"


  reply	other threads:[~2018-11-12  9:20 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 [this message]
2018-11-14  7:20   ` Henning Schild
2018-11-14 10:15     ` Jan Kiszka
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=20181112102006.6f52306a@md1za8fc.ad001.siemens.net \
    --to=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