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

[MacPorts]

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

 Also, just to help you understand why I'm pushing for this...

 I maintain four MacOS versions: 10.12, 10.13, 10.14, and 10.15. That's
 necessary for development reasons, as well as to deal with legacy software
 that won't run on the latest MacOS releases. Once 10.16 is released and
 stable, I'll have five.

 Anyway... Across those four versions, I maintain a consistent set of
 ports. Each of which needs to be updated at the same time, to ensure
 consistency. And over the past week, there have been two new versions of
 the Poppler port released. And in both instances, the upgrades required
 futzing with manual deactivation... four times. Not fun!

 Bear in mind that I'm not complaining about the frequent updates. Indeed,
 the great thing about MacPorts, is that you folks keep everything up-to-
 date relative to the various projects. And that's awesome!

 However, this particular case is irritating. Enough so, that I'm prepared
 to write a quick wrapper script to patch the Poppler port file with Ken's
 change, as part of my MacPorts upgrade workflow.

 But as a user, it's frustrating that I'm now at that point.

 Given that the proposed change isn't fragile -- it doesn't involve a
 moving target, such as patching the makefile for 'gobject-introspection'
 -- I simply can't understand the resistance...

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