[MacPorts] #57875: port:poppler shouldn't require C++14?!

MacPorts noreply at macports.org
Wed Jan 9 16:33:37 UTC 2019

#57875: port:poppler shouldn't require C++14?!
  Reporter:  RJVB     |      Owner:  dbevans
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  poppler  |

Comment (by RJVB):

 The less closely you follow updates, the more work (and the bigger the
 earthquake) each update can become.

 From that viewpoint it'd be better to allow concurrent installation of a
 "legacy port" (now 0.68 but could still be updated from time to time) and
 a "hot" port. The port:qt5 family already does something similar, for
 other reasons.
 Sadly "base" isn't really designed to make it easy to implement things in
 such a way that users can decide they're fine with building every poppler
 dependent against the "hot" poppler port.
 OTOH, we'd do this for a large part to avoid breakage in dependents, and
 in that light it's best simply to let the poppler port/version decision to
 the dependent ports and their maintainers.

 Back to the required clang version: according to
 https://clang.llvm.org/cxx_status.html, C++14 is already fully supported
 in clang 3.4! Very strange then that my AppleClang (which should be a 3.5
 version) doesn't even accept thread_local but well, it's from Apple ...
 they know better what's right for us don't they now ;)

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

More information about the macports-tickets mailing list