On Thu, 6 Feb 2025, Timothe Litt via curl-library wrote:
However, introducing them raises the issue of how to identify the version
that one has.
Typically, projects add something like "rc1" to the version string. curl has
never done that, but there are scripts that parse its version.
Actually we have. We did x.y.x-betaN releases for a while only a few decades
ago.
I'm not going to overwork this, so the release candidates are simply going to
be named x.y.x-rcN. A curl 1.2.3-rc2 release is then going to look like this:
$ ./src/curl -V
curl 1.2.3-rc2 (x86_64-pc-linux-gnu) libcurl/1.2.3-rc2 ...
Release-Date: [the date of the rc2 release]
...
The LIBCURL_* defines for the numerical version are then "hiding" the rc
state:
/* This is the version number of the libcurl package from which this header
file origins: */
#define LIBCURL_VERSION "1.2.3-rc2"
/* The numeric version number is also available "in parts" by using these
defines: */
#define LIBCURL_VERSION_MAJOR 1
#define LIBCURL_VERSION_MINOR 2
#define LIBCURL_VERSION_PATCH 3
#define LIBCURL_VERSION_NUM 0x010203
--
/ daniel.haxx.se || https://rock-solid.curl.dev
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
