[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

mimelib1 once again: library symbols, shlibs and soname

Hello again,

I'm still in the process of preparing mimelib1 packages for debian
unstable. Now I realized that the packages which I prepare do have
slightly different symbols than the old libmimelib1c2a package from

I tracked down the changes to some changes/patches I applied to the
library sources, but I don't know what to do about it.

First, I don't know much about the whole topic library, symbols, shlibs,
soname etc.

I compared the output of
'objdump -T /usr/lib/libmimelib.so.1 | grep \\.text | cut -b62-' for
libmimelib1c2a from debian/testing (built from kdepim/3.5.9-1) and the
packages that I prepared.

The first change I made to the sources is replacing strlcat/strlcpy with
strncat/strncpy. That change already produced a diff to the output of
objdump, see below.

Now what to do about it? should I simply bump the soname and binary
package names (from 1 to 2), request binNMUs for packages that do depend
on libmimelib1c2a and and forget about the whole issue? Or is there a
way to keep ABI compability with the help of a symbols file?


--- objdump_sid_libmimelib1c2a_1.1.2_kde	2009-04-27 16:44:22.000000000 +0200
+++ objdump_sid_libmimelib1c2a_1.1.2	2009-04-28 15:00:15.000000000 +0200
@@ -68,7 +68,6 @@
@@ -152,7 +151,6 @@
@@ -222,6 +220,7 @@
@@ -230,6 +229,7 @@
@@ -296,6 +296,7 @@
@@ -398,6 +399,7 @@
@@ -550,7 +552,6 @@
@@ -606,6 +607,7 @@
@@ -722,9 +724,11 @@
@@ -872,7 +876,6 @@

Reply to: