[MacPorts] #38907: Resolving libjpeg-turbo + jpeg Port conflicts

[MacPorts]

#38907: Resolving libjpeg-turbo + jpeg Port conflicts
----------------------------+----------------------
  Reporter:  davidfavor     |      Owner:  larryv
      Type:  enhancement    |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:
Resolution:                 |   Keywords:
      Port:  libjpeg-turbo  |
----------------------------+----------------------

Comment (by RJVB):

 I have been using libjpeg-turbo for about 3 years now myself, with a
 tweaked port:jpeg that can be co-installed but that acts mostly if not
 completely as a stub just to satisfy port dependencies (so I haven't kept
 it up to date). I'm now using libjpeg-turbo 2.0.4 (with a small patch so
 it registers a `compatibility_version` of 8 instead of 10, that feature
 mostly bites us in software from Linux, esp. if it switched from autoconf
 to cmake :-/)
 port:jpeg wouldn't be the first to be installed in subprefix, requiring a
 small patch to ports that really need it (or that want to provide an
 option to use the reference library).

 As others above I have never run into any problems because of a missing v9
 API, so I really don't understand what's the hold-up here. Even if
 port:jpeg provides the reference implementation I think that most users
 don't give a rat's ass about that while even more will probably appreciate
 any possible speed improvement in this department.

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