I'm packaging OpenJPH for pkgsrc. During updates, I noticed that OpenJPH makes the minor version of the shared library more important than other libraries do.
When installing OpenJPH 0.30.1 (and before), I see symlinks like this:
libopenjph.so -> libopenjph.so.0.30
libopenjph.so.0.30 -> libopenjph.so.0.30.1
libopenjph.so.0.30.1
For comparison, this is what it looks like for jpeg-turbo:
libjpeg.so -> libjpeg.so.8
libjpeg.so.8 -> libjpeg.so.8.3.2
libjpeg.so.8.3.2
In other words, I would expect that OpenJPH 0.29 and 0.30 with shared libraries libopenjph.so.0.29 and libopenjph.so.0.30 would be binary compatible (perhaps adding new symbols, but not changing or removing them) but as it's currently set up, "0.29" is the major version of the library, and every update is a major version bump.
Can you please follow what other libraries do? I.e.:
libopenjph.so -> libopenjph.so.0
libopenjph.so.0 -> libopenjph.so.0.30.1
libopenjph.so.0.30.1
Thanks!
(Perhaps that is NetBSD specific, but I think not.)
I'm packaging OpenJPH for pkgsrc. During updates, I noticed that OpenJPH makes the minor version of the shared library more important than other libraries do.
When installing OpenJPH 0.30.1 (and before), I see symlinks like this:
For comparison, this is what it looks like for jpeg-turbo:
In other words, I would expect that OpenJPH 0.29 and 0.30 with shared libraries
libopenjph.so.0.29andlibopenjph.so.0.30would be binary compatible (perhaps adding new symbols, but not changing or removing them) but as it's currently set up, "0.29" is the major version of the library, and every update is a major version bump.Can you please follow what other libraries do? I.e.:
Thanks!
(Perhaps that is NetBSD specific, but I think not.)