Previously, Loïc Minier reported a problem in how the libcamel library is versioned, see http://bugzilla.gnome.org/show_bug.cgi?id=321372. The problem can be seen in the filename /usr/lib/libcamel-1.2.so.0.0.0, which stays the same between each release.
For the distribution package maintainers, having possibly incompatible libraries with conflicting filenames is a headache. Regarding Evolution 2.6 for Debian, changing the soname would mean losing binary compatibility with other distributions. Although not ideal, that is currently being considered. What is important for us is to choose an soname that won't conflict with a potential future soname upstream. Therefore, we'd like to have your thoughts on if libcamel should have versioned soname or not, and what version scheme you will use. Our suggestion is that we use "-version-info $(LIBCAMEL_CURRENT): $(LIBCAMEL_REVISION):$(LIBCAMEL_AGE)" for 2.6 and upstream does the same for the next release with bumped versions. How does that sound? -- Øystein Gisnås Debian Evolution Maintainer Team
signature.asc
Description: Dette er en digitalt signert meldingsdel
_______________________________________________ Evolution-hackers mailing list [email protected] http://mail.gnome.org/mailman/listinfo/evolution-hackers
