>
> NB: The library name is libow.so.0.0.0. That is unrelated to packaging
> and needs to be fixed urgently -- a release should basically NEVER have
> a broken shared library soname like that.
>
Question is how to name the library... Current version is 2.6p4, so how
should we name the library.
libusb add their release to the name as well... like libusb-0.1.so.4.4.2
The format seem to be libX[-release].so.{current}:{revision}:{age}, so how
about changing the library-name to
libow-2.6.so.4.0.0, libow-2.6.so.5.0.0 etc..
I can't see any reason to use the age-field, since there are no reason to
use the libow to anything else
but the owfs-binaries (and probably libowcapi).
/Christian
------------------
I found some page at apple which describe the name convention.
http://developer.apple.com/documentation/DeveloperTools/glibtool/libtool_6.h
tml
Never try to set the interface numbers so that they correspond to the
release number of your package. This is an abuse that only fosters
misunderstanding of the purpose of library versions. Instead, use the
`-release' flag (see section Managing release information), but be warned
that every release of your package will not be binary compatible with any
other release.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
