[MacPorts] #38907: Resolving libjpeg-turbo + jpeg Port conflicts
#38907: Resolving libjpeg-turbo + jpeg Port conflicts ---------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ffmpeg ---------------------+-------------------------------- Since libjpeg-turbo released there are many Ports that could benefit from it's use, except dependencies in these Ports are for the jpeg Port which conflicts with libjpeg-turbo. Currently there appears to be no way to specify an "OR dependency"... like... depends_lib port:jpeg || port:libjpeg-turbo So is the correct way to fix this to change... depends_lib port:jpeg to... depends_lib path:lib/libjpeg.dylib which would then pass the dependency check for any Port that installed this library. Let me know if this is the correct fix. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/38907> MacPorts <http://www.macports.org/> Ports system for OS X
#38907: Resolving libjpeg-turbo + jpeg Port conflicts ----------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: ffmpeg | ----------------------+-------------------------------- Comment (by david@…): Oops... just noticed a formatting bug. The "OR dependency" should have looked like... {{{ depends_lib port:jpeg || port:libjpeg-turbo }}} -- Ticket URL: <https://trac.macports.org/ticket/38907#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#38907: Resolving libjpeg-turbo + jpeg Port conflicts ----------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: ffmpeg | ----------------------+-------------------------------- Comment (by david@…): Looks like this won't work for libjpeg-turbo, because jpeg9 breaks API/ABI compatibility with jpeg8 and libjpeg-turbo uses the jpeg8 API. Grumble... Let me know if this is the correct way to resolve this type of conflict, for possible future work. Thanks. -- Ticket URL: <https://trac.macports.org/ticket/38907#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#38907: Resolving libjpeg-turbo + jpeg Port conflicts ----------------------------+----------------------------- Reporter: david@… | Owner: rmstonecipher@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: libjpeg-turbo | ----------------------------+----------------------------- Changes (by ryandesign@…): * cc: openmaintainer (removed) * owner: macports-tickets@… => rmstonecipher@… * type: request => enhancement * port: ffmpeg => libjpeg-turbo Old description:
Since libjpeg-turbo released there are many Ports that could benefit from it's use, except dependencies in these Ports are for the jpeg Port which conflicts with libjpeg-turbo.
Currently there appears to be no way to specify an "OR dependency"... like...
depends_lib port:jpeg || port:libjpeg-turbo
So is the correct way to fix this to change...
depends_lib port:jpeg to...
depends_lib path:lib/libjpeg.dylib
which would then pass the dependency check for any Port that installed this library.
Let me know if this is the correct fix.
Thanks.
New description: Since libjpeg-turbo released there are many Ports that could benefit from it's use, except dependencies in these Ports are for the jpeg Port which conflicts with libjpeg-turbo. Currently there appears to be no way to specify an "OR dependency"... like... {{{ depends_lib port:jpeg || port:libjpeg-turbo }}} So is the correct way to fix this to change... {{{ depends_lib port:jpeg }}} to... {{{ depends_lib path:lib/libjpeg.dylib }}} which would then pass the dependency check for any Port that installed this library. Let me know if this is the correct fix. Thanks. -- Comment: If libjpeg-turbo were a drop-in compatible replacement for jpeg (which I thought it was, but which you've pointed out as of jpeg 9 it isn't anymore) then yes the solution would be to change all `port:jpeg` dependencies in all ports to `path:lib/libjpeg.dylib:jpeg`. -- Ticket URL: <https://trac.macports.org/ticket/38907#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38907: Resolving libjpeg-turbo + jpeg Port conflicts ----------------------------+----------------------------- Reporter: david@… | Owner: rmstonecipher@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: libjpeg-turbo | ----------------------------+----------------------------- Comment (by rmstonecipher@…): Ryan, David,[[br]] The libjpeg-turbo [http://www.libjpeg-turbo.org/About/Jpeg-9 commentary on jpeg 9, SmartScale, etc.] gives me the impression that the changes to ijg jpeg are non-standard, academic in nature, and not widely-adopted.[[br]] Could we not modify the path dependency to depend on libjpeg-turbo by default and let jpeg 9, which seems to be drifting away from standards- compliance, be the alternative library?[[br]] Could Portfile voodoo be used to force systems upgrading jpeg-dependent packages to deactivate jpeg 9, install libjpeg-turbo, and rebuild against it? -- Ticket URL: <https://trac.macports.org/ticket/38907#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts