Hello,
Does dmidecode follow semantic versioning (1) and
what does that mean for binaries that do not have an API?
Was this release called 3.5 rather than 3.4.1 because an old feature
was dropped:
3d68350 dmidecode: Drop the CPUID exception list
I don't have a pressing need for it but most of the commits in dmidecode
are to support new hardware and in an ideal world, those changes would
be back-ported to stable release branches. I know that's extra work for
the maintainer
but it would be interesting to know of that has been requested before
and what the conclusion was.
Right now if I really need to support new hardware, with an old release,
I'd just backport the relevant
commits manually as other distros may already be doing.
The context is a discussion (2) about what's a sensible approach to
fixing CVEs for dmidecode on a stable release in Yocto, and other
distros I suppose.
Thanks,
../Randy
1) https://semver.org/
2)
https://lists.openembedded.org/g/openembedded-core/message/184561?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3ACreated%2C0%2Cdmidecode%2C20%2C2%2C0%2C100151225
--
# Randy MacLeod
# Wind River Linux
