[Bert Huijben]
> How did we handle the transition from apr 0.9 to 1.X?
I complained that we were breaking ABI compatibility, and it turned
into a miniature flame war, and in the end, nothing happened. Then,
later, when we decided to ship apr 1.x in the -deps tarball, someone
added a big warning to the release notes about the ABI ramifications.
In Debian, as someone mentioned already, I've been maintaining a patch
to handle this more or less "correctly":
svn://svn.debian.org/pkg-subversion/src/1.7.x/debian/patches/apr-abi
I changed the SONAMEs in the libraries, _and_ changed the name of the
package that provides them. Thus your old apps, linked to the old
libsvn and the old libapr, and your new apps, linked to the new libsvn
and the new libapr, could coexist on your system and everything would
work perfectly. Eventually, if you recompiled or upgraded all your old
apps, you could uninstall the old libsvn, apr, and apr-util packages.
Tracking this was no different from tracking any other "when can I
uninstall this old library" scenario.
I (once again) suggest something like that be done officially for apr2,
though I note I was also sloppy about hardcoding the 0 -> 1 in part of
that patch; the official solution should be a bit more thorough.
--
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
