babl @0.1.74: library minor version is 0.0.0

[ryandesign (Ryan Carsten Schmidt)]

In babl @0.1.68 the library minor compatibility version was 168.0.0:

$ otool -L /opt/local/lib/libbabl-0.1.dylib
/opt/local/lib/libbabl-0.1.dylib:
	/opt/local/lib/libbabl-0.1.0.dylib (compatibility version 168.0.0, current version 168.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.250.1)
	/opt/local/lib/liblcms2.2.dylib (compatibility version 3.0.0, current version 3.8.0)

In 0.1.72 and 0.1.74, the library minor compatibility version has dropped to 0.0.0:

$ otool -L /opt/local/lib/libbabl-0.1.dylib
/opt/local/lib/libbabl-0.1.dylib:
	/opt/local/lib/libbabl-0.1.0.dylib (compatibility version 0.0.0, current version 0.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.250.1)
	/opt/local/lib/liblcms2.2.dylib (compatibility version 3.0.0, current version 3.8.0)

This means that programs don't work anymore:

Incompatible library version: /opt/local/bin/gimp-2.10 requires version 168.0.0 or later, but /opt/local/lib/libbabl-0.1.0.dylib provides version 0.0.0

This probably arose because babl switched its build system to meson and did not take the necessary steps to specify their library versioning properly.

I cannot find an upstream bug tracker for babl to report this to them.

[Dave-Allured (Dave Allured)]

Ryan, it looks like babl uses Gitlab issues for bug tracking. Try the following. Just poking my nose in here. Thanks for taking initialive on this.

​https://gitlab.gnome.org/GNOME/babl/-/issues

[ryandesign (Ryan Carsten Schmidt)]

Thanks, I've filed it here: ​https://gitlab.gnome.org/GNOME/babl/-/issues/52

[mascguy (Christopher Nielsen)]

Reassign babl-related tickets to me

[mascguy (Christopher Nielsen)]

Replying to ryandesign:

Thanks, I've filed it here: ​https://gitlab.gnome.org/GNOME/babl/-/issues/52

It looks like this problem still exists, and upstream ticket still open. Will follow-up on this.