On Sun, 2013-04-14 at 09:02 -0400, Colin Walters wrote: > Is "libpng" the new canonical name for 1.6?
Its a symlink to libpng16.pc which is something libpng upstream's "make install" provides. > I assume there was a reason > it was listed last. It looks like the current logic came from: > > https://git.gnome.org/browse/gdk-pixbuf/commit/?id=ddedf5a2c2c63bfe8d6f04376cf2bba215a5eb19 > > Which is a not very enlightening commit message. It looks like the > Fedora 18 "libpng" package provides both libpng.pc and libpng15.pc. > RHEL6 has the same except it's libpng12.pc too. My Ubuntu 12.10 VM has > libpng12 with just libpng12.pc, no libpng.pc. The more interesting change is: https://git.gnome.org/browse/gdk-pixbuf/commit/configure.ac?id=d430bc4df3314a88cd538474d26ff7764d1f408c and following that to the bugzilla 'For this to make sense, I changed the order so that a version specific dep, such as libpng15 or libpng12, is found before just "libpng".' I'm not sure I entirely follow that logic. > My main concern with this patch was ensuring that people aren't getting > a suddenly ancient and deprecated libpng, but that seems unlikely, so > unless there are other comments I can take care of turning this into > "git format-patch" style and pushing upstream. I think the intent of the symlink is to provide the system with a default libpng to use in the absence of a specific version requirement. As the code stands today, each time a new libpng comes out, gdk-pixbuf will need changes before it will be able to use it. In the meantime, it will potentially link against something old, e.g. 1.2, since 1.2 is in the LSB 4.X spec so most LSB like systems would have 1.6 and 1.2. If we can justify changing this upstream, that would be great :). It may be worth adding libpng16 into the list too so everything is covered too. Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
