Hello,
I'm a bit confused about the library versioning scheme of the
owfs-libs.
Commonly a shared library foo hast the name “libfoo.so.M.I.P” where M
is the major number, I the minor number and P the patch-level. As long
as M does not change binary compatibility is given. This allows
applications to use a more recent binary compatible version than the
one it was linked again.
The owfs libs have names like “libfoo-2.7.so.17.0.0”. Does this comply
with the common scheme? Is 17 the API-Version or a patch-level?
MfG
bmg
--
„Des is völlig wurscht, was heut beschlos- | M G Berberich
sen wird: I bin sowieso dagegn!“ | berbe...@fmi.uni-passau.de
(SPD-Stadtrat Kurt Schindler; Regensburg) | www.fmi.uni-passau.de/~berberic
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
