From: Dan Murphy <dmurphy@ti.com>
To: <meta-arago@arago-project.org>
Subject: [dunfell/master] [RFC PATCH] branding: Add branding-core-next to aid in migration
Date: Thu, 14 Jan 2021 10:47:43 -0600 [thread overview]
Message-ID: <20210114164743.2340-1-dmurphy@ti.com> (raw)
Add a core-next brand branding type to be able to re-direct the recipe
preferred providers or versions to highest PV'd recipe. The
branding-core should indicate the current version to build if not the
highest version.
For the purpose of an example the Arago distribution will be migrating
from the 5.4 kernel to the 5.10 during the 2021 time frame. In order to
assist with a smoother migration the distribution needs to be able to
build the 5.4 kernel for the core brand and build the 5.10 kernel for
the core-next.
Once the transition from 5.4->5.10 kernel is done then the
PREFERRED_VERSION in the branding-core.inc can be removed.
From: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
.../conf/distro/include/branding-core-next.inc | 6 ++++++
meta-arago-distro/conf/distro/include/branding-core.inc | 3 +++
2 files changed, 9 insertions(+)
create mode 100644 meta-arago-distro/conf/distro/include/branding-core-next.inc
diff --git a/meta-arago-distro/conf/distro/include/branding-core-next.inc b/meta-arago-distro/conf/distro/include/branding-core-next.inc
new file mode 100644
index 000000000000..d65c5db2f379
--- /dev/null
+++ b/meta-arago-distro/conf/distro/include/branding-core-next.inc
@@ -0,0 +1,6 @@
+# Special "migration" branding for testing components that are to be updated in LTS migration
+
+require branding-core.inc
+
+PREFERRED_VERSION_linux-ti-staging = ""
+PREFERRED_VERSION_u-boot-ti-staging = ""
diff --git a/meta-arago-distro/conf/distro/include/branding-core.inc b/meta-arago-distro/conf/distro/include/branding-core.inc
index cab9831be9f9..a0abc6230780 100644
--- a/meta-arago-distro/conf/distro/include/branding-core.inc
+++ b/meta-arago-distro/conf/distro/include/branding-core.inc
@@ -11,3 +11,6 @@ ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1"
# Raise priority for sample IPC FW images
ALTERNATIVE_PRIORITY_pn-ti-ipc-rtos = "15"
+
+PREFERRED_VERSION_linux-ti-staging = "5.4%"
+PREFERRED_VERSION_u-boot-ti-staging = "2020.01%"
--
2.29.2
next reply other threads:[~2021-01-14 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 16:47 Dan Murphy [this message]
2021-01-14 18:24 ` [dunfell/master] [RFC PATCH] branding: Add branding-core-next to aid in migration Denys Dmytriyenko
2021-01-14 18:46 ` Dan Murphy
2021-01-14 18:58 ` Denys Dmytriyenko
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=20210114164743.2340-1-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=meta-arago@arago-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.