[maemo-developers] [maemo-developers] packages: soname (0c2a, etc)

From: Adrian Neumaier adrian at firehand.org
Date: Wed Jul 26 11:04:39 EEST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Murray Cumming schrieb:
> The soname is the package suffix, such as 0c2a seen here:
> http://packages.debian.org/unstable/libs/libsigc++-2.0-0c2a
> 
> I believe that these suffixes are changed whenever either
> - A new version of g++, with a new C++ ABI, is used.
> or
> - A new version of libstdc++, with a new ABI, is used.

Thats correct.

> I don't know what the 0, c, 2, or a parts of the suffix mean, or if suffix
> is just changed arbitrarily. I can't find an overview of these in the
> debian documentation.

- -0 is the package revision. So in the end this whole thing means:
libsigc++ Version 2.0, Package revision 0, build with gcc-4.x
c2a was introduced during the transition of gcc-3.3 to gcc-4.0 in
unstable. gcc3.3 and 4.x have incompatible abi's, so if your lib is
compiled with the 4.x suite, you cannot link use it with a program
compiled with 3.3 or earlier.

You could search on the debian-devel mailinglist for a detailed
description. I cannot remember the exact meaning for c2a either :-)

> Maybe we could use the appropriate debian sonames, but we probably don't
> have the same combinations of C++ and libstdc++ ABIs so there might be no
> appropriate choice.
> 
> 
> I could remove the soname/suffix from the package name, which would
> involve a few more changes to the debian/ stuff than I'd like to make, so
> I thought I'd check first.

Bad idea :-) Those sonames are in debian to indicate that the abi has
changed, and thus the packages depending on that lib needs to be recompiled.

Cheers
Adrian
- --
GPG Key ID: 42C33D97 | Reg. User #255628 (http://counter.li.org)
Fingerprint: 239D 7006 3CF0 8951 9FDA CA63 EF5C C95A 42C3 3D97
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBRMciF2cvsWk2zYzGAQq3nQ//b7285+iRS0u4npIPB/rnOz0L9UXcf090
q7XK1SypMsph6Zz+WOIfj5rqLZogqWi2q+P1Cw1vzZm7E9zQ+KHkPZq3GgzfhyRW
xApbrViUD6PB3p40LOpuRTGTXTQXWrmoIG9DHiMGGKdmvO1noPAAYOKICrjp+Spe
0HQgG0fo9Uc46l3ee1Ceq3cIvMHIhaMUtrLdIrbOzB0uUrqQ95/YKULhpNdqUqzU
hBsHofJjoljPD9S+amhfuger1e4M75YxEm8IMN2KZPKNwKrd7zL69UkjRSGPLkHV
dXvxp+JBTC7y9vl+ETjbTiVjSz923NUQ9vz/eFfAHPKzapt+Z5rlo8plMXRBSuxh
4PMtv8jZ25AUzp8yiMH0BDm9WI3nDm33gyDk0/YdAePZlRaZWnKTjh2AkNHYB3Mj
/a3RKktt3ySJ/UWaISLBh3kuJ0xsKZM0+E0znkAOEo/dDPDs6Hl7wPO+pH1YxXfr
hbka0cVEki47PlzsZQRKUvk2pKGkwo+IVKaO4f52tX4ajH2gguufA+sVvVEf8wZ9
WB0LF+zALva+Nnc3OBFGMel79qtCZOOnNlZSbZ6VWv3+2AdQN5A6u8/G3M+KAlIV
PPWXaYJmVVGiRMe0K8Pw7CrAY2oAxHqKTsOGMO1I9RNDm4jTqiGcqCMque4b5MzO
JxKln1UsxaY=
=cik2
-----END PGP SIGNATURE-----

More information about the maemo-developers mailing list