[MacPorts] #67273: hdf5: either make +fortran a default or make it a standalone port?

[MacPorts]

#67273: hdf5: either make +fortran a default or make it a standalone port?
---------------------------+----------------------
  Reporter:  barracuda156  |      Owner:  eborisch
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.8.1
Resolution:                |   Keywords:
      Port:  hdf5          |
---------------------------+----------------------

Comment (by Dave-Allured):

 The current HDF5 build system supports building the core C API without
 components.  However, it does not support building any of the wrapper
 API's as stand-alone.  I can think of several ways to do this for
 MacPorts.

 1.  Wait for upstream to add component capability to their build system.
 It looks like this might take a while.

 2.  Patch the current build system to enable building, for example, the
 fortran API on top of a previous core C API build.  The configuration
 dependency issues may be complicated.

 3.  Following a previous core C API build, make another build for core
 plus fortran, for example.  Then install only the fortran libs and include
 files; in effect throwing away the files from the second core build.  This
 may be easier than (2).

-- 
Ticket URL: <https://trac.macports.org/ticket/67273#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS