[MacPorts] #38907: Resolving libjpeg-turbo + jpeg Port conflicts
MacPorts
noreply at macports.org
Sat Jul 13 20:11:39 UTC 2019
#38907: Resolving libjpeg-turbo + jpeg Port conflicts
----------------------------+--------------------------------
Reporter: davidfavor | Owner: macports-tickets@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: libjpeg-turbo |
----------------------------+--------------------------------
Comment (by devernay):
Is there any update on this?
Ports that depend specifically on the new jpeg9 API (there is very
probably none) could keep the dependency on port:jpeg, but most (if not
all) ports should depend on path:lib/libjpeg.dylib:jpeg
Major Linux distributions now use libjpeg-turbo instead of libjpeg9
(Fedora, Debian, Mageia, openSUSE).
Official binaries for Mozilla and Chrome also use libjpeg-turbo.
Also note that libjpeg-turbo is now an Official ISO/ITU-T Reference
Implementation (see https://jpeg.org/items/20190204_press.html ).
There should be no more discussion on changing depend_libs port:jpeg to
depend_libs path:lib/libjpeg.dylib:jpeg.
The only remaining discussion should be whether MacPorts should default to
libjpeg-turbo as its default JPEG library. I would vote YES for that,
given the very strong support.
--
Ticket URL: <https://trac.macports.org/ticket/38907#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list