Hi, On Sat, May 18, 2013 at 12:05:26PM +0200, Hans de Goede wrote: > > I've been in the Linux distro "business" for a long time now, and > there is a HUGE cost to ABI breaking library releases. And almost > always the old and new version will need to be maintained in parallel > for a long time. For example gtk+ (aka gtk-1.0) is still around, > while we've 10 years of gtk-2.0 behind us, and 2 years of > gtk-3.0! Also notice there have been 8 years between gtk-2.0 > and gtk-3.0 and the latest gtk-2 release, gtk-2.32 is fully > backward ABI compat with gtk-2.0
I haven't got any shared library maintenance experience myself, but from what I've read distros seem to encourage the use of ELF symbol versioning to generate correct package version dependencies. For Debian, dpkg-gensymbols and dpkg-shlibdeps will do it, I guess RPM has something similar. However, surprisingly few libraries make use of ELF symbol versioning, zlib is one prominent example I know of (besides glibc). These docs have some info on symbol versioning. if you are interested: http://plan99.net/~mike/writing-shared-libraries.html http://www.akkadia.org/drepper/goodpractice.pdf http://www.akkadia.org/drepper/dsohowto.pdf Also, do you know http://upstream-tracker.org/ ? HTH Johannes ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
