Problems with the libcdio shared object name. Sigh. Planning on putting out another release 0.78.1 and removing 0.78. Comments?
A candidate tarball is http://bashdb.sf.net/libcdio-0.78.1.tar.gz I encourage folks to try it out to see that I haven't messed up again. Thanks. >From Janos Farkas: What prompted me to write this mail is more serious, IMHO, apparently the library soname has been changed. While this happens to libraries, it's quite uncommon that the next version of "libcdio.so.7" is "libcdio.so.6". I sometimes avoid newer versions with soname changes even if the change is reasonable, because I then can't get rid of the older programs using the older library. But this is not what I'd call entirely reasonable, of course. The culprit is obvious after you become a bit more familiar with the awkwardness that is libtool :) --- libcdio-0.77/lib/driver/Makefile.am 2006-03-14 12:05:16.000000000 +0000 +++ libcdio-0.78/lib/driver/Makefile.am 2006-10-11 12:38:18.000000000 +0000 @@ -47,3 +47,3 @@ libcdio_la_CURRENT := 7 libcdio_la_REVISION := 0 -libcdio_la_AGE := 0 +libcdio_la_AGE := 1 The trouble is, that libtool does some mangling with these values, and the real soname is a system-dependent arithmetic on these numbers. Since libcdio's CURRENT wasn't incremented along with AGE, its soname major number was decremented... R. Bernstein writes: > In ftp://ftp.gnu.org/pub/gnu/libcdio/libcdio-0.78.tar.gz > > If the 0.77 was the Peter Creath release, this one should be called > the Burkard Plaum and Flameeyes release. > > Thanks to everyone who has helped in making this release possible. And > yet again, thanks to Steve Schultz for the use of his wonderful OSX > hardware. > > > _______________________________________________ > Libcdio-devel mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/libcdio-devel > _______________________________________________ Libcdio-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/libcdio-devel
