On 25 June 2018 at 13:21, Niko Tyni wrote: | On Sun, Jun 24, 2018 at 08:38:00AM -0500, Dirk Eddelbuettel wrote: | | > GSL_CURRENT=24 | > GSL_REVISION=0 | > GSL_AGE=1 | | > I am stumped. Why does the '24' version not get through? | | I think you'd need to reset the age to zero, as explained in the | configure.ac comments and | | https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html | | Reading those comments, it looks to me like upstream will never | end up with an SONAME of libgsl.so.24 so you'd be free to use that.
I missed the point of 'major propagates only at age 0'. Good catch. That should do that -- so I could open the door to changing the soname at each release. | But wouldn't it be smoother to reinstate the deprecated symbols for now, | and remove them at the next upstream SONAME bump or a Debian specific | transition? I could revert this: AH_VERBATIM([GSL_DISABLE_DEPRECATED], [/* Disable deprecated functions and enums while building */ #define GSL_DISABLE_DEPRECATED 1]) and comment it back out. If I tried, can you try and see if it helped you (before I upload, say)? I am somewhat as to as to who needs what. I got a few GSL bug reports on this and tried to accomodate them, but maybe I reverted the logic in my head. Hm. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
