[Proj] ABI version numbers

[Greg Troxel]

Sebastiaan Couwenberg <sebastic at xs4all.nl> writes:

> On 10/27/2017 12:37 PM, Roger Oberholtzer wrote:
>> On Fri, Oct 27, 2017 at 12:05 PM, Kristian Evers <kreve at sdfe.dk> wrote:
>>> Not that I am aware of. There is this https://github.com/OSGeo/proj.4/issues/501 though, which gives you some idea of how the binaries how changed over time.
>>>
>>> If you volunteer to create an overview of the ABI versions I am sure we can find somewhere in the docs to put it :-)
>> 
>> The reason I ask is that openSUSE use these numbers when naming the
>> package. The numbers do come from the build:
>> 
>> 4.8.0 -> libproj.so.0.7.0
>> 4.9.2 -> libproj.so.9.1.0
>> 4.9.3 -> libproj.so.12.0.0
>> 
>> And so on. So they name the packages libproj0-4.8.0, libproj9-4.9.2,
>> libproj12-4.9.3.
>> 
>> I accused them of randomly generating the 0, 9 and 12. They said - no
>> - it comes from the library itself. Which it indeed does seem to do.
>> So I thought I would see if this is recorded somewhere.
>
> The SOVERSION is calculated using the libtool -version-info arguments.
>
>  https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
>
> The ABI tracker has an overview of the SOVERSION for past releases:
>
>  https://abi-laboratory.pro/tracker/timeline/proj/

Thanks - that's a really useful analysis.

(not directed at Bas of course)

It would also be good if proj avoided changing the solib version if
there isn't an actual ABI change, and tried to avoid ABI changes unless
really necessary.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 162 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20171109/b3367692/attachment.sig>