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

MacPorts noreply at macports.org
Wed Apr 24 16:41:37 PDT 2013


#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


More information about the macports-tickets mailing list