![](https://secure.gravatar.com/avatar/ad7c76b9aa8758315397d0dfb15fc222.jpg?s=120&d=mm&r=g)
On Jan 7, 2010, at 7:27 PM, Krzysztof KosiĆski wrote:
However... glibmm has additional issues. This note at the top of their documentation page covers it:
This documentation is for the gtkmm-2.4 and gnomemm-2.6 APIs. There is an older gtkmm API called gtkmm-2.0 which can be installed in parallel. The gtkmm-2.4 name refers to the API/ABI series and not the release version. For instance, gtkmm 2.10 is a version of the gtkmm-2.4 API.
This note is unrelated to my question. It refers to the gtkmm ABI break that was made between 2.0 and 2.4 releases (a long time ago). Since then the ABI was preserved. For example I have gtkmm-2.4 version 2.18.2.
Yes... but I was trying to point out the *consequence* of such things.
That is, keeping minor version numbers in lockstep was not required, so for quite some time the glibmm team did *not* keep them up. And if they do not keep things up, then when we go to grab our dependencies, we have to take the numbers they have.
(better news is that for latest-and-greatest they appear to be updating far more frequently)