[MacPorts] #62165: graphviz: Update to 2.46.0

MacPorts noreply at macports.org
Fri Mar 12 02:12:20 UTC 2021


#62165: graphviz: Update to 2.46.0
---------------------------------------+------------------------
  Reporter:  jarrodmillman             |      Owner:  ryandesign
      Type:  update                    |     Status:  accepted
  Priority:  Normal                    |  Milestone:
 Component:  ports                     |    Version:
Resolution:                            |   Keywords:
      Port:  graphviz, graphviz-devel  |
---------------------------------------+------------------------

Comment (by Smattr):

 Hello, I am one of Graphviz' de facto maintainers. Thanks Jarrod for
 pointing me here.

 I'm not a Macports pro, but I think the Portfile referred to above is
 https://github.com/macports/macports-ports/blob/master/graphics/graphviz-
 devel/Portfile or https://github.com/macports/macports-
 ports/blob/master/graphics/graphviz/Portfile. Some thoughts:
 * Graphviz still does the development releases, but I honestly don't know
 who is using them. The reality is that they are no more or less stable or
 tested than the "stable" releases, so I would simply like to move to a
 more frequent release cadence.
 * The `post-patch` step in those Portfiles that is doing stuff related to
 libc++ is I believe trying to work around
 https://gitlab.com/graphviz/graphviz/-/issues/163. We resolved this in
 Graphviz commit 3dd185241646d10149c86899f3a99beb51fce5d9 (a mere 5 years
 after @ryandesign diligently reported it...) which made it into release
 2.46.0, so I believe this should no longer be necessary.
 * We had to unfortunately yet again migrate where Graphviz downloads are
 hosted, so the `livecheck` probably doesn't work. See
 https://gitlab.com/graphviz/graphviz/-/issues/1371 for more details.
 * The Portfiles have various references to Qt4, but we dropped Qt4 support
 in Graphviz commit 32abc6416f2e87f00b009e7f526102c5d937a933 which made it
 into release 2.46.1. I'm unsure how much pain migrating to Qt5 causes you.
 * Maybe the GVEdit regex is trying to match this line in the source?
 https://gitlab.com/graphviz/graphviz/-/blob/master/cmd/gvedit/mainwindow.cpp#L273
 I was not aware of this until just now and I don't know why we give GVEdit
 a separate version number instead of just the Graphviz version number
 itself.

 Graphviz maintenance is challenging because (a) most of our users are on
 Windows or macOS, (b) most of the maintainers have no access to Windows or
 macOS, and (c) many users are using Graphviz via something else (e.g.
 PyGraphviz), which makes them hugely productive but often unable to
 explain how to reproduce their issues using pure Graphviz. I myself have
 no GUI environment on my Graphviz development machine, so I mostly try not
 to touch GVEdit as I have no way of running or testing it.

 If there's anything we can do on our side to ease future packaging, please
 let us know. For my own part, I've been trying to strip as much "magic"
 out of the Graphviz build system, reduce dependencies, and remove non-
 portable code.

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


More information about the macports-tickets mailing list