latest version of libpng

[Dagobert Michelsen]

Hi Riccardo,

> Am 27.03.2015 um 17:11 schrieb Riccardo Mottola <rmottola at opencsw.org>:
>>> On my own box I and up having libpng3.. Just to know about this oddity.
>>> 
>>> There are some security updates, I'll try my best updating libpng, but wanted to now this oddity first.
>> If you don’t introduce another soname it should be fine, otherwise the same restrictions apply
>> as to e.g. the OpenSSL transition:
>> http://wiki.opencsw.org/project-openssl
>> Although it should be less of a problem now due to direct linking, but AFAIK this has not been
>> tested enough.
> 
> what do you mean by "soname change"? I see that libpng15 introduced a new soname, bu hides it with a link
> 
> so libpng.so is then linked to libpng15.so.15.13.0
> 
> I thought of adding libpng16.so.16.xxx to follow this reasoning.

Essentially yes, the reasing is explained here:
  http://www.opencsw.org/manual/for-maintainers/shared-libraries.html


Best regards

— Dago

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20150328/1422cebd/attachment-0001.p7s>