Since the conversion to autotools, i3status -h and i3status -v no longer report the "full" i3status version. Instead of reporting a string like 2.13-100-gf119d9b (2021-02-08, branch "testing"), it simply reports 2.13. This means that a patched or custom compiled version is indistinguishable from an actual release binary, which is obviously bad for diagnostics.
The cause is that in the old Makefile, -DVERSION was set to the contents of ${I3STATUS_VERSION}, whereas autotools sets the value of VERSION directly in config.h (to ${VERSION}, not ${I3STATUS_VERSION}).
Rather than try to change the VERSION macro back to the old format (which might break things that make assumptions about autotools' format of VERSION), I just updated the i3status -h and i3status -v code to directly use I3STATUS_VERSION instead of VERSION.
Since the conversion to autotools,
i3status -handi3status -vno longer report the "full" i3status version. Instead of reporting a string like2.13-100-gf119d9b (2021-02-08, branch "testing"), it simply reports2.13. This means that a patched or custom compiled version is indistinguishable from an actual release binary, which is obviously bad for diagnostics.The cause is that in the old
Makefile,-DVERSIONwas set to the contents of${I3STATUS_VERSION}, whereas autotools sets the value ofVERSIONdirectly inconfig.h(to${VERSION}, not${I3STATUS_VERSION}).Rather than try to change the
VERSIONmacro back to the old format (which might break things that make assumptions about autotools' format ofVERSION), I just updated thei3status -handi3status -vcode to directly useI3STATUS_VERSIONinstead ofVERSION.