branding: Add branding-core-next to aid in migration
RFC PATCH 1/1 branding: Add branding-core-next to aid in migration
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 <[email protected]>
--- .../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
meta-arago-distro/conf/distro/include/branding-core-next.inc new file +6 -0
@@ -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 = ""
meta-arago-distro/conf/distro/include/branding-core.inc +3 -0
@@ -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%"
Signature · 1 line
2.29.2
Quoted 39 lines · Dan Murphy
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_VERSIONin the branding-core.inc can be removed.From: Dan Murphy <[email protected]>
Signed-off-by Dan Murphy <[email protected]>--- .../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.incmeta-arago-distro/conf/distro/include/branding-core-next.inc new file +6
-0@@ -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 = ""meta-arago-distro/conf/distro/include/branding-core.inc +0
-0
meta-arago-distro/conf/distro/include/branding-core.inc ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1" · line 15
Quoted 5 lines
meta-arago-distro/conf/distro/include/branding-core.inc +2
-0@@ -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%"
Should also include linux-ti-staging-rt and linux-ti-staging-systest
Quoted 4 lines
meta-arago-distro/conf/distro/include/branding-core.inc +1
-0+PREFERRED_VERSION_u-boot-ti-staging = "2020.01%"Signature · 1 line
2.29.2
Denys
Quoted 41 lines · Denys Dmytriyenko
Quoted 40 lines · Dan Murphy
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_VERSIONin the branding-core.inc can be removed.From: Dan Murphy <[email protected]>
Signed-off-by Dan Murphy <[email protected]>--- .../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
meta-arago-distro/conf/distro/include/branding-core-next.inc new file +6
-0@@ -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 = ""meta-arago-distro/conf/distro/include/branding-core.inc +0
-0@@ -11,3 +11,6 @@ ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1"
Quoted 6 lines
meta-arago-distro/conf/distro/include/branding-core.inc ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1" · line 15
Quoted 4 lines
meta-arago-distro/conf/distro/include/branding-core.inc +2
-0# Raise priority for sample IPC FW images ALTERNATIVE_PRIORITY_pn-ti-ipc-rtos = "15" + +PREFERRED_VERSION_linux-ti-staging = "5.4%"Should also include linux-ti-staging-rt and linux-ti-staging-systest
Thanks I will add them in v2
Do you see anything wrong with this approach?
Dan
Quoted 49 lines · Dan Murphy
Denys
Quoted 37 lines · Denys Dmytriyenko
Quoted 36 lines · Dan Murphy
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_VERSIONin the branding-core.inc can be removed.From: Dan Murphy <[email protected]>
Signed-off-by Dan Murphy <[email protected]>--- .../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.incmeta-arago-distro/conf/distro/include/branding-core-next.inc new file +6
-0@@ -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 = ""meta-arago-distro/conf/distro/include/branding-core.inc +0
-0Quoted 9 lines
meta-arago-distro/conf/distro/include/branding-core.inc ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1" · line 14
Quoted 7 lines
meta-arago-distro/conf/distro/include/branding-core.inc +2
-0@@ -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%"Should also include linux-ti-staging-rt and linux-ti-staging-systest
Quoted 3 lines
Thanks I will add them in v2
Do you see anything wrong with this approach?
In general, looks good to me.
Signature · 1 line
Denys