Upgrading libpng: shall we move to 1.4.x or 1.5.x?

[Michael Schwendt]

On Mon, 21 Nov 2011 16:26:02 -0500, TL (Tom) wrote:

> > With
> 
> >   pkgconfig(libpng) = 1.2.46
> >   pkgconfig(libpng12) = 1.2.46
> 
> > once libpng12.pc gets removed from the distribution, the dep-chains
> > break, of course.
> 
> > As a temporary work-around, you could have provided that thing manually
> > in the libpng-devel upgrade instead of including the actual libpng12.pc
> > file:
> 
> >   Provides: pkgconfig(libpng12) = %{version}-%{release}
> 
> > Any configure script or .pc file using a hardcoded "libpng12" name
> > would fail to build, but that would be better IMO than offering an
> > incomplete broken compat package that confuses the buildroots.
> 
> Well, I don't have any objection to doing it that way, but exactly what
> about this "confuses the buildroots"?

In the buildroot, pkg-config queries on 'libpng12' succeed and let the
build job continue when in fact it should terminate early ... because
even if the source were compatible with the new headers, -lpng12 would
fail due to missing files.