layers: set LAYERSERIES_COMPAT with honister
PATCH 1/1 layers: set LAYERSERIES_COMPAT with honister
From: Kai Kang <[email protected]>
Set LAYERSERIES_COMPAT with 'honister' which align with oe-core.
--- meta-filesystems/conf/layer.conf | 2 +- meta-gnome/conf/layer.conf | 2 +- meta-initramfs/conf/layer.conf | 2 +- meta-multimedia/conf/layer.conf | 2 +- meta-networking/conf/layer.conf | 2 +- meta-oe/conf/layer.conf | 2 +- meta-perl/conf/layer.conf | 2 +- meta-python/conf/layer.conf | 2 +- meta-webserver/conf/layer.conf | 2 +- meta-xfce/conf/layer.conf | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-)
meta-filesystems/conf/layer.conf +1 -1
@@ -15,4 +15,4 @@ LAYERVERSION_filesystems-layer = "1" LAYERDEPENDS_filesystems-layer = "core openembedded-layer" -LAYERSERIES_COMPAT_filesystems-layer = " hardknott" +LAYERSERIES_COMPAT_filesystems-layer = "honister"
meta-gnome/conf/layer.conf +1 -1
@@ -17,7 +17,7 @@ LAYERVERSION_gnome-layer = "1" LAYERDEPENDS_gnome-layer = "core openembedded-layer networking-layer" -LAYERSERIES_COMPAT_gnome-layer = " hardknott" +LAYERSERIES_COMPAT_gnome-layer = "honister" SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += "\ faenza-icon-theme->gdk-pixbuf \
meta-initramfs/conf/layer.conf +1 -1
@@ -16,7 +16,7 @@ BBFILE_PATTERN_meta-initramfs := "^${LAYERDIR}/" BBFILE_PRIORITY_meta-initramfs = "8" LAYERDEPENDS_meta-initramfs = "core" -LAYERSERIES_COMPAT_meta-initramfs = " hardknott" +LAYERSERIES_COMPAT_meta-initramfs = "honister" SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \ dracut->virtual/kernel \
meta-multimedia/conf/layer.conf +1 -1
@@ -31,4 +31,4 @@ LAYERVERSION_multimedia-layer = "1" LAYERDEPENDS_multimedia-layer = "core meta-python" -LAYERSERIES_COMPAT_multimedia-layer = " hardknott" +LAYERSERIES_COMPAT_multimedia-layer = "honister"
meta-networking/conf/layer.conf +1 -1
@@ -17,7 +17,7 @@ LAYERDEPENDS_networking-layer = "core" LAYERDEPENDS_networking-layer += "openembedded-layer" LAYERDEPENDS_networking-layer += "meta-python" -LAYERSERIES_COMPAT_networking-layer = " hardknott" +LAYERSERIES_COMPAT_networking-layer = "honister" LICENSE_PATH += "${LAYERDIR}/licenses"
meta-oe/conf/layer.conf +1 -1
@@ -42,7 +42,7 @@ LAYERVERSION_openembedded-layer = "1" LAYERDEPENDS_openembedded-layer = "core" -LAYERSERIES_COMPAT_openembedded-layer = " hardknott" +LAYERSERIES_COMPAT_openembedded-layer = "honister" LICENSE_PATH += "${LAYERDIR}/licenses"
meta-perl/conf/layer.conf +1 -1
@@ -15,4 +15,4 @@ LAYERVERSION_perl-layer = "1" LAYERDEPENDS_perl-layer = "core openembedded-layer" -LAYERSERIES_COMPAT_perl-layer = " hardknott" +LAYERSERIES_COMPAT_perl-layer = "honister"
meta-python/conf/layer.conf +1 -1
@@ -14,6 +14,6 @@ LAYERVERSION_meta-python = "1" LAYERDEPENDS_meta-python = "core (>= 12) openembedded-layer" -LAYERSERIES_COMPAT_meta-python = " hardknott" +LAYERSERIES_COMPAT_meta-python = "honister" LICENSE_PATH += "${LAYERDIR}/licenses"
meta-webserver/conf/layer.conf +1 -1
@@ -17,7 +17,7 @@ LAYERVERSION_webserver = "1" LAYERDEPENDS_webserver = "core openembedded-layer" -LAYERSERIES_COMPAT_webserver = " hardknott" +LAYERSERIES_COMPAT_webserver = "honister" LICENSE_PATH += "${LAYERDIR}/licenses"
meta-xfce/conf/layer.conf +1 -1
@@ -19,7 +19,7 @@ LAYERDEPENDS_xfce-layer += "multimedia-layer" LAYERDEPENDS_xfce-layer += "meta-python" LAYERDEPENDS_xfce-layer += "networking-layer" -LAYERSERIES_COMPAT_xfce-layer = " hardknott" +LAYERSERIES_COMPAT_xfce-layer = "honister" SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += "\ openzone->gdk-pixbuf \
Signature · 1 line
2.17.1
Quoted 5 lines · kai
From: Kai Kang <[email protected]>
Set
LAYERSERIES_COMPATwith 'honister' which align with oe-core.
I think it's bad practice to claim honister support this early in its development cycle. It won't happen with well-maintained layers like meta-oe, but if some less frequently updated layer sets the compatibility with honister now and then doesn't get necessary updates to stay compatible with honister in next 4 months, then whole purpose of LAYERSERIES_COMPAT will get broken just by claiming the compatibility too soon (without even knowing what final honister will contain).
Changing it after release freeze in oe-core seems much better time to do it.
The same does apply on the meta-qt5 PR you've sent today
https://github.com/meta-qt5/meta-qt5/pull/416/commits
Cheers,
Quoted 8 lines · Martin Jansa
On Fri, Jun 4, 2021 at 3:44 AM kai <[email protected] <mailto:[email protected]>> wrote:
From: Kai Kang <[email protected]
<mailto:[email protected]>>Set
LAYERSERIES_COMPATwith 'honister' which align with oe-core.
Quoted 7 lines
I think it's bad practice to claim honister support this early in its development cycle. It won't happen with well-maintained layers like meta-oe, but if some less frequently updated layer sets the compatibility with honister now and then doesn't get necessary updates to stay compatible with honister in next 4 months, then whole purpose of
LAYERSERIES_COMPATwill get broken just by claiming the compatibility too soon (without even knowing what final honister will contain).Changing it after release freeze in oe-core seems much better time to do it.
The same does apply on the meta-qt5 PR you've sent today https://github.com/meta-qt5/meta-qt5/pull/416/commits <https://urldefense.com/v3/__https://github.com/meta-qt5/meta-qt5/pull/416/commits__;!!AjveYdw8EvQ!Kd76LvM-JcgNBu85RB8Bu2U6MF7jgfI31fh0o1hXL0VPVFMaEEBpol_tM3o5gwAD5A$>
Cheers,
Got it. Thanks very much.
I've comment on the meta-qt5 PR that too long strings in LAYERSERIES_COMPAT will cause layer index complains:
WARNING: YPCompatibleVersion.name: dunfell gatesgarth hardknott: length 28 exceeds maximum (25), truncating
So what is policy to keep old codenames in LAYERSERIES_COMPAT? Is that ok to keep latest 2(hardknott and honister), please?
Regards,
Signature · 2 lines
Kai Kang Wind River Linux
Then I believe layer index should be fixed to support longer values, there are layers which are compatible with multiple releases and it works fine with bitbake/oe-core, layer index parsing shouldn't be more strict than the mechanism which is using these variables.
Quoted 44 lines · Kai
On 6/4/21 4:52 PM, Martin Jansa wrote:
Quoted 5 lines · kai
From: Kai Kang <[email protected]>
Set
LAYERSERIES_COMPATwith 'honister' which align with oe-core.I think it's bad practice to claim honister support this early in its development cycle. It won't happen with well-maintained layers like meta-oe, but if some less frequently updated layer sets the compatibility with honister now and then doesn't get necessary updates to stay compatible with honister in next 4 months, then whole purpose of
LAYERSERIES_COMPATwill get broken just by claiming the compatibility too soon (without even knowing what final honister will contain).Changing it after release freeze in oe-core seems much better time to do it.
The same does apply on the meta-qt5 PR you've sent today
https://github.com/meta-qt5/meta-qt5/pull/416/commits
<https://urldefense.com/v3/__https://github.com/meta-qt5/meta-qt5/pull/416/commits__;!!AjveYdw8EvQ!Kd76LvM-JcgNBu85RB8Bu2U6MF7jgfI31fh0o1hXL0VPVFMaEEBpol_tM3o5gwAD5A$>Cheers,
Got it. Thanks very much.
I've comment on the meta-qt5 PR that too long strings in
LAYERSERIES_COMPATwill cause layer index complains:WARNING: YPCompatibleVersion.name: dunfell gatesgarth hardknott: length 28 exceeds maximum (25), truncating
So what is policy to keep old codenames in
LAYERSERIES_COMPAT? Is that ok to keep latest 2(hardknott and honister), please?Regards,
--
Kai Kang
Wind River Linux
Quoted 3 lines · Martin Jansa
Then I believe layer index should be fixed to support longer values, there are layers which are compatible with multiple releases and it works fine with bitbake/oe-core, layer index parsing shouldn't be more strict than the mechanism which is using these variables.
Hi,
I agree with Martin, we have examples of compatibility since sumo, we will surely split but this is an unreasonable limit.
A.A.
Quoted 36 lines · Kai
Quoted 31 lines · Martin Jansa
Quoted 5 lines · kai
From: Kai Kang <[email protected]>
Set
LAYERSERIES_COMPATwith 'honister' which align with oe-core.I think it's bad practice to claim honister support this early in its development cycle. It won't happen with well-maintained layers like meta-oe, but if some less frequently updated layer sets the compatibility with honister now and then doesn't get necessary updates to stay compatible with honister in next 4 months, then whole purpose of
LAYERSERIES_COMPATwill get broken just by claiming the compatibility too soon (without even knowing what final honister will contain).Changing it after release freeze in oe-core seems much better time to do it.
The same does apply on the meta-qt5 PR you've sent today https://github.com/meta-qt5/meta-qt5/pull/416/commits
Cheers,
Got it. Thanks very much.
I've comment on the meta-qt5 PR that too long strings in
LAYERSERIES_COMPATwill cause layer index complains:WARNING: YPCompatibleVersion.name: dunfell gatesgarth hardknott: length 28 exceeds maximum (25), truncating
So what is policy to keep old codenames in
LAYERSERIES_COMPAT? Is that ok to keep latest 2(hardknott and honister), please?Regards,
--
Kai Kang
Wind River Linux