[MacPorts] #62165: graphviz: Update to 2.46.0

[MacPorts]

#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):

 Sorry for delay; I didn’t actively monitor this ticket, assuming I would
 get email updates.

 [The next paragraph discusses your URLs and you may want to just skip it
 and jump to the solution in the paragraph after that]

 I think the first URL you posted is the “source code” link on the Gitlab
 releases page, right? That one is unhelpful and we would delete/omit it if
 we could. AFAIK Gitlab’s `release-cli` client we use to create our
 releases has no way to do this. What you’re after is what we confusingly
 refer to as the “portable source” which is the second URL you posted.

 I think a sophisticated downstream consumer like Macports might actually
 be better off side-stepping the portable source (which is not as portable
 as its name implies), and cloning the Graphviz repository directly. We tag
 our releases so you would just have to clone tag `2.46.0` and refer to our
 CI¹ (which also side-steps the portable source). This will allow you to,
 e.g., enable the quartz dependencies that are disabled in the portable
 source. You have greater dependency requirements this way (Flex, Bison, …)
 but you get to build whatever you want with fewer assumptions.

   ¹ https://gitlab.com/graphviz/graphviz/-/blob/main/.gitlab-
 ci.yml#L77-112 and
 https://gitlab.com/graphviz/graphviz/-/blob/main/ci/build.sh#L47-53

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