On Mon, 7 Oct 2019 at 12:39, Ole Streicher <[log in to unmask]> wrote:
>
> Hi all,
>
> I just found the AST library (which is used f.e. in SaoImageDS9) updated
> to version 9, and I am quite happy to still see it updated. I would like
> to update the Debian package for the library ASAP.
>
> The library has a number of additions in the API/ABI; however there are
> also a number of symbols that disappeared. This makes the library binary
> incompatible with the previous version 8.7.2.
>
> Usually this is soved by increasing "soversion" of the shared library;
> which is however not set for AST. Since the update of the major version
> number also happened at this time: can one just take the major version
> number here? Otherwise, what is your rule to increase the major version
> number?
Hi Ole,
Apologies - I had forgotten that I said I would look into
updating the soname used by AST for the next release. How would it be
if I adopted the scheme described at
https://phab.enlightenment.org/w/autotoolsintegration/ under
"Versioning of the shared library"? That is:
soname_current = package_minor + package_major
soname_revision = package_micro
soname_age = package_minor
David
########################################################################
To unsubscribe from the STARDEV list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=STARDEV&A=1
|