are you saying we need additional ports like readline50 readline 51 readline 52? Regards, Elias On Mar 20, 2007, at 1:48 PM, Vincent Lefevre wrote:

On 2007-03-19 21:37:19 -0700, source_changes@macosforge.org wrote:

...

Revision: 22947 http://trac.macosforge.org/projects/macports/changeset/ 22947 Author: pipping@macports.org Date: 2007-03-19 21:37:19 -0700 (Mon, 19 Mar 2007)

Log Message: ----------- * bump version to 5.2 * add links for 5.[01]'s libs (should fix #9897, #9335, please confirm)

I'm not sure that this is correct. If the library name has changed, this normally mean that the API is not backward compatible, in which case adding symlinks would be incorrect.

-- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/ blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS- Lyon) _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev

On 2007-03-20 17:19:31 +0100, Elias Pipping wrote:

some output from otool:

/opt/local/lib/libreadline.5.2.dylib (compatibility version 5.0.0, current version 5.2.0)

doesn't this mean 5.2 and 5.0 are compatible?

No, this doesn't mean anything. Interface versions are different from the software versions. For instance, otool says for neon: /opt/local/lib/libneon.26.dylib (compatibility version 27.0.0, current version 27.3.0) while the library files are: /opt/local/lib/libneon.26.0.3.dylib /opt/local/lib/libneon.26.dylib -> libneon.26.0.3.dylib /opt/local/lib/libneon.a /opt/local/lib/libneon.dylib -> libneon.26.0.3.dylib /opt/local/lib/libneon.la Here you can see that there are no relations between interface versions (27.0.0, 27.3.0) and the library version (0.26.3). And software linked with /opt/local/lib/libneon.26.dylib (such as svn) will continue to work when neon is upgraded if the interface is compatible: /opt/local/lib/libneon.26.dylib will point to a new file, but that's not a problem. The problem with readline is somewhere else. It should be fixed so that software is linked to /opt/local/lib/libreadline.5.dylib instead of /opt/local/lib/libreadline.5.*.dylib. -- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)