[MacPorts] #34457: Let hdf5-18 maintainer revision bump all its dependents

[MacPorts]

#34457: Let hdf5-18 maintainer revision bump all its dependents
---------------------------------------------+------------------------------
  Reporter:  florian@…                       |       Owner:  macports-tickets@…                   
      Type:  enhancement                     |      Status:  closed                               
  Priority:  Normal                          |   Milestone:                                       
 Component:  ports                           |     Version:                                       
Resolution:  fixed                           |    Keywords:                                       
      Port:  hdf5-18, py-h5py, gdal, netcdf  |  
---------------------------------------------+------------------------------

Comment(by florian@…):

 Like you said rev-upgrade seems to check only for renames. I wonder
 whether the exact procedure is documented somewhere. The easiest way to
 ensure that rev-upgrade correctly picks up the hdf5 upgrade is to rename
 the library with each new library version, e.g., from libhdf5.7.dylib to
 libhdf5.8.dylib. I would consider the fact that the version in the
 filename of the lib does not reflect its compatibility version a bug
 although I believe this is intended by the hdf5 guys in order to print the
 compatibility warning.

 It would be great if rev-upgrade would pick up a change in the
 "compatibility version". But then we have to file a bug against hdf5 that
 they increase the ''compatibility version'' for each release that would
 break the API. Right now they increment only the "current version"
 although they claim the versions are incompatible:
 {{{
 $ port activate hdf5-18 @1.8.8_0+universal
 $ otool -L /opt/local/lib/libhdf5.7.dylib
 /opt/local/lib/libhdf5.7.dylib:
         /opt/local/lib/libhdf5.7.dylib (compatibility version 8.0.0,
 current version 8.2.0)
         /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current
 version 1.2.7)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 125.2.11)

 $ port activate hdf5-18 @1.8.9_0+universal
 $ otool -L /opt/local/lib/libhdf5.7.dylib
 /opt/local/lib/libhdf5.7.dylib:
         /opt/local/lib/libhdf5.7.dylib (compatibility version 8.0.0,
 current version 8.3.0)
         /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current
 version 1.2.7)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 125.2.11)
 }}}

 It seems there are several possibilities but to me the most robust right
 now looks like changing the install name of the hdf5 library each time it
 is updated so that rev-upgrade kicks in.

-- 
Ticket URL: <https://trac.macports.org/ticket/34457#comment:13>
MacPorts <http://www.macports.org/>
Ports system for Mac OS