Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 319821

Summary: media-libs/libpng-1.2-43-r3: ebuild doesn't install libpng12.pc
Product: Gentoo Linux Reporter: Rafal Lalik <rafallalik>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Rafal Lalik 2010-05-15 12:01:16 UTC
Ebuild doesn't install libpng12.pc which may be required by some apps (in example, chromium-6.0 requires libpng12.pc thus configure fails; pkg-config --list-all shows that libpng12.pc required by cairo is missing, however configure from x11-libs/cairo doesn't complain about libpng12.pc).

Best,
Rafal
Comment 1 Samuli Suominen (RETIRED) gentoo-dev 2010-05-15 12:08:28 UTC
umm, no.  

media-libs/libpng-1.2-43-r2 installs libpng12.pc like it should.

but if your recently upgraded to libpng-1.4, then you need to rebuild packages like cairo, pango, libglade, gtk+, and then the rest packages from "revdep-rebuild --library libpng12.so.0" list
Comment 2 Rafal Lalik 2010-05-15 12:18:50 UTC
Sorry, I meant libpng-1.2.43-r3

From my experience some apps stil needs libpng:12 (break libraries on runtime or linking time).

Rule is, if package provides *.pc file then you should install it. Other deleopers trust, when you have libpng12.pc in your system then you have this lib which they expect and the don't care about 1.4, 9999 or something else.

Further more, if libpng-1.2 and 1.4 are in different slots then probably API is changed and both are required, for older and newer apps.
Comment 3 Samuli Suominen (RETIRED) gentoo-dev 2010-05-15 12:26:14 UTC
(In reply to comment #2)
> Sorry, I meant libpng-1.2.43-r3

nah, -r3 is for binary-only programs and not for building packages, it's designed to be co-installed with libpng-1.4 for backwards compability

closing as a dupe of bug 319807 then

*** This bug has been marked as a duplicate of bug 319807 ***