[MacPorts] #60718: sundials @3.1.2 update to versions 4.1.0 and 5.3.0

[MacPorts]

#60718: sundials @3.1.2 update to versions 4.1.0 and 5.3.0
-----------------------+--------------------
  Reporter:  rwirth    |      Owner:  (none)
      Type:  update    |     Status:  closed
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:  fixed     |   Keywords:
      Port:  sundials  |
-----------------------+--------------------
Changes (by mascguy):

 * status:  new => closed
 * cc: mascguy (added)
 * resolution:   => fixed


Comment:

 Replying to [comment:1 ryandesign]:
 > The sundials and sundials2 ports currently conflict with another. This
 is not desired. If we are to keep several ports around for SUNDIALS at
 different versions, they should install to different places and not
 conflict with one another.

 The various `sundials` ports are now segregated, eliminating these
 headaches. Fixed per issue:63631

 > We currently have a sundials port at version 3.1.2 and a sundials2 port
 at version 2.7.0, but all of the ports in MacPorts that use SUNDIALS
 depend on sundials2 presumably because they are not compatible with
 version 3. And you're saying that versions 4 and 5 exist and they also
 break compatibility. It sounds like maybe we need to rename the sundials
 port to sundials3 and add sundials4 and sundials5 ports and just accept
 that we need to keep many different versions around.

 Based on my testing, the four dependents of our various `sundials` ports,
 are all set: One (`petsc`) uses `sundials2`, while the other three
 (`deal.ii`, `cantera`, and `octave`) all work fine with `sundials5`.

 Of note, `deal.ii` and `cantera` are broken due to other issues, so they
 currently don't build. But I've validated that they properly find/use
 `sundials5`, so that's one less thing to worry about.

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