On Mon, 11 May 2026 at 11:32, Alexander Kanavin <[email protected]> wrote:
> 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 ?
On further thought, the class should support only
major.minor.point[.subpoint] schemes.
The problem with removing only the last number is when upstream issues:
x.y.z -> x.y.z.zz, we update to that, and then there's
x.y.z.zz -> x.y.z+1 - this would not be considered a stable update,
even though it is.
It's a bit complicated to get it right :)
So basically:
def get_majmin_version_regex(d):
pv = d.getVar('PV')
v_parts_majmin = pv.split('.')[:2]
return '\.'.join(v_parts_majmin)
...
UPSTREAM_STABLE_RELEASE_REGEX = "${MAJMIN_VERSION_REGEX}(\.\d+)+"
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#236795):
https://lists.openembedded.org/g/openembedded-core/message/236795
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]]
-=-=-=-=-=-=-=-=-=-=-=-
