From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH] conf: Add value 'next' to LAYERSERIES_CORENAMES
Date: Mon, 19 Nov 2018 13:16:04 +0100 [thread overview]
Message-ID: <20181119121604.28640-1-mosipov@ilbers.de> (raw)
If you need to express the fact that your layer requires the
layer version higher than existing release corename,
use the value 'next'.
Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
---
RECIPE-API-CHANGELOG.md | 8 ++++++++
meta/conf/layer.conf | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index af12994..e3bed1b 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -16,6 +16,14 @@ not just packaged as before.
- a lot of debhelpers will help .. or complain
fix the issues or override the helpers (see example-raw)
+### Set LAYERSERIES_COMPAT_* when an own layer is defined
+
+When defining an own layer LAYERSERIES_COMPAT_mylayer_root_name has to be set,
+the possible values are listed in the variable LAYERSERIES_CORENAMES.
+
+If you need to express the fact that your layer requires the
+layer version higher than existing release corename, use the value 'next'.
+
### location of image artifacts
Align with OpenEmbedded and place image artifacts in a per-machine folder placed
diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index ec34d85..a38ab97 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -11,7 +11,7 @@ BBFILE_COLLECTIONS += "core"
BBFILE_PATTERN_core = "^${LAYERDIR}/"
BBFILE_PRIORITY_core = "5"
-LAYERSERIES_CORENAMES = "v0.6"
+LAYERSERIES_CORENAMES = "v0.6 next"
# This should only be incremented on significant changes that will
# cause compatibility issues with other layers
--
2.11.0
next reply other threads:[~2018-11-19 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 12:16 Maxim Yu. Osipov [this message]
2018-11-22 13:03 ` 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=20181119121604.28640-1-mosipov@ilbers.de \
--to=mosipov@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