[MacPorts] #17044: evince wants old libopenjeg

[MacPorts]

#17044: evince wants old libopenjeg
-----------------------------------+----------------------------------------
  Reporter:  frstan at bellsouth.net  |       Owner:  devans at macports.org
      Type:  defect                |      Status:  assigned           
  Priority:  Normal                |   Milestone:  Port Bugs          
 Component:  ports                 |     Version:  1.6.0              
Resolution:                        |    Keywords:  evince openjpeg lib
      Port:  evince                |  
-----------------------------------+----------------------------------------

Comment(by devans at macports.org):

 Replying to [comment:4 blb@…]:
 > Replying to [comment:2 devans@…]:
 > > Actually, I take that back as I don't see openjpeg as a direct
 dependency of evince, so it must be a dependency of a dependency of
 evince.
 > >
 >
 > evince does have a dep on jpeg, so perhaps configure, when it sees
 openjpeg available, uses that instead?

 No, that doesn't make sense to me.  jpeg is the traditional JPEG 6 library
 and openjpeg is an implementation of the newer JPEG 2000 file format
 which is a different thing altogether.  As far as I can tell, the only
 thing that uses openjpeg right now is gimp-jp2 which is a plugin for
 GIMP (gimp2) which reads and writes images in the JPEG 2000 file format.
 The port gimp is a metaport.  It doesn't do anything itself,
 only has dependencies on other ports that together make a nice GIMP
 installation.

 The error looks like one that is seen when starting GIMP if the gimp-jp is
 not up to date, that is, was built against the older version
 of openjpeg.  The cure is to update/rebuild gimp-jp2.

 I can't understand how this can be a build time problem -- that is one
 that appears when building something.

 Can you be more detailed in describing the problem?

 For instance, exactly what command are you executing when you see the
 problem.  Is it a port install or update command?
 If so, please run the command with the -d option and include the full
 debugging output that demonstrates the problem.

 It's possible that your ports aren't up to date.

 Please


 {{{
 sudo port -d selfupdate
 port outdated
 }}}

 and then run
 {{{
 sudo port upgrade <portname>
 {{{

 for any outdated ports listed.  Then try again.

 Sorry, I'm not being much help here -- more information is needed.

-- 
Ticket URL: <http://trac.macports.org/ticket/17044#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS