On Friday, July 27, 2012 8:19:44 AM UTC-4, kapouer wrote:
>
> The version you use in the package name (libv8-3.10.8) reflects the 
> soname version of the library. Upstream v8 doesn't guarantee ABI 
> compatibility of libv8 releases (because it is quite difficult to do so), 
> but, as indicated by data like 
> http://www.upstream-tracker.org/versions/v8.html 
> you can safely assume the soname version to be 3.10.8 instead of 
> 3.10.8.23, 
> because 3.10.8.24 (most likely) won't break ABI/API compatibility. 
>
> If you understand this, you realize you can't choose a soname version of 
> 3.12.16, because it is likely to be ABI/API incompatible with 3.12.16.xx 
> at some point. In that case you either use the full version, or wait for 
> that branch to reach a stable state. 
>

Thank you. That is another part of the gyp compiling puzzle I addressed. 
Linux expects something like libv8.so.3 and I additionally provide soft 
links for libv8.so, libv8.so.3.11 and libv8.so.3.11.10.
The compile end result with proper soname in CentOS 5.8:

> Provides: libv8.so.3()(64bit)
> Requires(interp): /bin/sh /bin/sh
> Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> Requires(post): /bin/sh
> Requires(postun): /bin/sh
> Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) 
> libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.4)(64bit) libm.so.6()(64bit) 
> libm.so.6(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) 
> libpthread.so.0(GLIBC_2.2.5)(64bit) libstdc++.so.6()(64bit) 
> libstdc++.so.6(CXXABI_1.3)(64bit) libstdc++.so.6(GLIBCXX_3.4)(64bit) 
> libv8.so.3()(64bit) rtld(GNU_HASH)
> Processing files: v8-devel-3.11.10-1.el5
> Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> Requires: libv8.so.3()(64bit) python(abi) = 2.4 v8 = 3.11.10-1.el5


I would like to also know how do you determine the 4th number which 
indicates stability fixes? I did not see any info into ChangeLog. So far, I 
only know the major, minor, build and repo revision.

-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users

Reply via email to