Fix incorrect format of library version in meson
Right. ABI probably won't change but good to have it right.
(Just wondering, is there any reason for this way of numbering? If ABI change did just
C+1.0.0, would it cause some problems?)
We're doing all this just because we want to ensure that autotools and meson produce the same versions. Autotools uses Libtool's weird
current:revision:agescheme to specify a compact set of "interface versions" which are supported, which is then translated to the system's actual versioning scheme. If we were using only Meson we could use the latter directly.
I guess this is just a boatload of legacy-ness. https://www.gnu.org/software/libtool/manual/libtool.html#Versioning
Well, I plan to remove the autotools (see !4 (closed)) so the question is whether doing
C+1.0.0wouldn't be nicer when we won't have to care about autotools.
Again, in reality there probably won't be an ABI change in the libchamplain-0.12.so library. In the future there could be a "stable" release without the version as part of the library name (libchamplain.so) and the necessary ABI changes could be made then.
If we're throwing autotools away anyway, how about just using the project version, then? That would make the next libchamplain release have
At some point this could become
Hmm, I think the filename should reflect API/ABI compatibility changes. With such naming you won't know whether an application linked against
libchamplain-0.12.so.0.12.19can be used on a system with
libchamplain-0.12.so.0.12.18because you don't know whether there was an API addition between the releases or not and whether the application doesn't use the new API.
Hmm, true. I'll leave the libtool-style versioning in place in my MR for now. This can be revisited later.