[MacPorts] #58574: poppler upgrade fails if older poppler is installed

MacPorts noreply at macports.org
Wed Oct 14 09:23:56 UTC 2020


#58574: poppler upgrade fails if older poppler is installed
----------------------+----------------------
  Reporter:  RobK88   |      Owner:  dbevans
      Type:  defect   |     Status:  reopened
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.5.4
Resolution:           |   Keywords:
      Port:  poppler  |
----------------------+----------------------

Comment (by ryandesign):

 Chris, I don't know what you're referring to when you ask about more
 customized error handling. If you're suggesting MacPorts base should give
 portfiles an opportunity to run code after a build fails, I don't know
 what that would be good for, except to implement the workaround you've
 discussed in this ticket which I do not recommend implementing. Since a
 portfile is a Tcl file it could technically already implement anything you
 want. poppler could override the build phase so that failures are ignored,
 and then implement its own detection of the failure condition and respond
 appropriately. I do not want to spend any time overcomplicating the
 poppler port to implement this; we should fix the real problem instead.

 Ken, in the upstream bug report I pointed out that libdazzle is such a
 much simpler piece of software. If you don't like that one, you can check
 any other ports that depend on gobject-introspection. As far as "reliably
 show[ing] the bug", one only needs to add some printf statements to g-ir-
 scanner to see what paths it was invoked with or what it will set the DYLD
 variable to to see whether it is right or wrong.

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


More information about the macports-tickets mailing list