On Sat, 9 May 2026 at 07:30, <[email protected]> wrote:
> +def get_majmin_version_regex(d):
> + pv = d.getVar('PV')
> + v_parts = pv.split('.')
> + if len(v_parts) == 1:
> + return pv
> + else:
> + return '\.'.join(v_parts[:-1])
To be honest, I would not special-case the len(v_parts) == 1, as the
class becomes somewhat inconsistent:
x -> x.1 is supported
x.y -> x.y.1 is not supported (instead it treats the stable versions
as x.y -> x.y+1 )
These are two different schemes, so I would not mix them in a single
class, and support only:
x.y -> x.y+1
x.y.z -> x.y.z+1
x.y.z.zz -> x.y.z.zz+1
etc
For x->x.1 we can make a different class,
'upstream-stable-release-append-number' maybe ?
> +MAJMIN_VERSION_REGEX = "${@get_majmin_version_regex(d)}"
> +UPSTREAM_STABLE_RELEASE_REGEX = "${MAJMIN_VERSION_REGEX}\.\d"
\.\d should be (\.\d+)+ to allow numbers bigger than 9 and multiple
.number parts one after another.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#236794):
https://lists.openembedded.org/g/openembedded-core/message/236794
Mute This Topic: https://lists.openembedded.org/mt/119226368/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
