[xmlsec] versioning and library naming policies

Aleksey Sanin aleksey at aleksey.com
Wed Apr 2 08:40:10 PST 2003

Does not seem like it's a hard rule these days:

go:/usr/lib/ uname -a
SunOS go 5.8 Generic_108528-13 sun4u sparc SUNW,Sun-Blade-100
go:/usr/lib/ ls | grep "\-[.0-9]*.so" | wc -l


Wan-Teh Chang wrote:

>  Note that I do not agree with all the recommendations
>of APR's Version Numbering document.  I just wanted
>to point out that there are already proposed solutions
>to this problem.
>One issue is that Unix vendors typically do not like
>including the MAJOR version number in the library
>name, for example,
>      libFOO-MAJOR.so
>Instead, Unix vendors typically want to have
>      libFOO.so.MAJOR
>as the library file name (which could be a symbolic
>link to libFOO.so.MAJOR.MINOR or something like that)
>and the library's SONAME, and
>      libFOO.so
>as a symbolic link pointing to the latest MAJOR
>version.  This reflect the "multiple runtimes, one
>SDK" design.  This issue might come up if a Unix
>vendor would like to include your library in their

More information about the xmlsec mailing list