Status: New
Owner: ----
New issue 594 by aradici: Better handling of SONAME
http://code.google.com/p/v8/issues/detail?id=594
Hi,
as a result of bug http://code.google.com/p/v8/issues/detail?id=151 a
SONAME was added to the library.
Unfortunately the way the SONAME is currently being used could cause big
pain when more and more programs will start depending on libv8 on Debian.
We would really like the SONAME to be handled in the way most libraries are
handling it: changing the SONAME only when the binary compatibility is
broken.
To be clearer, quoting from [1]
" If a new version of a library package breaks a currently existing and
working package (the ABI), the SONAME version number should be bumped up,
or the change be reverted, or both. By bumping up the SONAME version
number, the old binaries which used to link to the old version of the
library should be able to run with the old library, and the new and the old
libraries can coexist.
Signs of binary incompatibility include: function declaration change,
change of "struct" contents, and changing semantics of functions (hard to
detect)."
Please let me know if you have any questions.
Cheers
Antonio
[1]
http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#sonameapiabi
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
