FS#15306 - [libtiff] libtiff.so.4 symlink

Attached to Project: Arch Linux
Opened by Ulf Winkelvos (uwinkelvos) - Sunday, 28 June 2009, 22:18 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 01 July 2009, 16:25 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Debian based distributions symlink libtiff.so.3.6.1 and upwards to libtiff.so.4, as there was some accidental abi change. So software developed on these systems that links to that "version" refuses to run on Arch. This seems to be some dirty hack, but when i compile the latest version (4.0.0 beta3) i get the following version numbers:

pkg/usr/lib/libtiff.so -> libtiff.so.5.0.0
pkg/usr/lib/libtiff.so.5 -> libtiff.so.5.0.0
pkg/usr/lib/libtiff.so.5.0.0

Obviously the developers have adopted the debian versioning and so it should be save to create the symlink in the package.

Additional info:
http://www.asmail.be/msg0055439498.html
http://bbs.archlinux.org/viewtopic.php?id=45393
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 01 July 2009, 16:25 GMT
Reason for closing:  Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 28 June 2009, 22:38 GMT
This is a bad idea as you know. Anyway I assing to maintainer that have the last opinion about this.

If you need the dirty hack, do it in your system. This make libtiff to follow dirty ways.

If posible to rebuild the soft, do it, in other case if is a closed-source, send mail to authors with the request, or do the direty hack with the symlink, making the soft in and undefined behaviour. The ABI is incompatible, can work, or not...
Comment by Jan de Groot (JGC) - Sunday, 28 June 2009, 23:00 GMT
I don't think we should implement this. Debian has some other soname differences also, one example is pcre/libpcre3. Though they package 7.6, their soname is .so.3, while upstream uses .so.0 (they don't bump soname after ABI change it seems).
Comment by Ulf Winkelvos (uwinkelvos) - Monday, 29 June 2009, 00:01 GMT
As stated here http://www.asmail.be/msg0055468514.html libtiff 4.0.0 and i hope (though i might be wrong) for consitency reasons all following versions in 4.x will create symlinks to .so.5. If im right there sould not be any ABI troube, as .so.4 will never be released. I am not sure about that, but Eric will know better. :)
Comment by Jan de Groot (JGC) - Monday, 29 June 2009, 06:09 GMT
The current version uses .so.3, and the next version uses .so.5, there's no reason to add symlinks to any of these here.
Comment by Allan McRae (Allan) - Monday, 29 June 2009, 15:45 GMT
There is no guarantee that our so.3 or the future so.5 are ABI compatible with whatever Debian did to force it to bump the soname to so.4. In fact it is very likely that things would break as Debian would not have bumped the soname for no reason...

So this is more of a Can't Fix than a Won't Fix.

Loading...