For this the definition of _ELFUTILS_PREREQ would have to be changed
to
include a sub-minor version number. Right after the release the tree
certainly cannot be tagged with the version number of the next release.
In glibc I tag the tree with 2.x.90 after the release of 2.x.
I fiddled the magic so _ELFUTILS_VERSION is a 1000 times bigger now and
includes the z if version is x.y.z instead of x.y. The _ELFUTILS_PREREQ
macro is the same, you can still only check for >= x.y granularity but now
configure.ac can say 0.140.90 and this "rounds to ceiling":
#define _ELFUTILS_PREREQ(major, minor) \
((_ELFUTILS_VERSION + 999) / 1000 >= ((major) * 1000 + (minor)))
Please verify it all seems sane. With this, we'll have to make sure we
always use .z for "next .y+=1 pre-test" and never do x.y.1 "minor
updates"
and such. (The de facto policy now is already to only ever release x.y
versions.)
Thanks,
Roland