From: Thiago F. de M. <sig...@hy...> - 2010-03-31 18:17:37
|
In contact with Debian developers, appeared some doubts. Above our talk: > On Tue, Mar 30, 2010 at 10:03:05AM -0400, Michael Hanke wrote: > > On Tue, Mar 30, 2010 at 09:41:29AM -0300, Thiago Franco Moraes wrote: > > > Michael, Why did you compile the sigar as a static lib? It was because > > > a compiling problem? > > > > No, compiling as a shared library works fine (I tested it, including > > linking the bindings against it). However, we cannot ship an unversioned > > shared library in Debian. > > Yes, but in several cases the Debian maintainer "invented" a soversion, > mostly 0.0.0 or something like this to enable easy upgrades. > > > At the same time we cannot use the current > > version, since this is an SVN snapshot and we don't know whether > > upstream will break API/ABI before the release. > > Teaching upstream about sonames does not harm - this finally reduces the > packaging work later on because you do not need to invent it. Upstream knows about versions and they do use them already. However, this SVN snapshot still uses the old stable version -- nobody knows how often they will break the ABI before they release -- after all this is a development snapshot. I only say that we should not step forward with shared-lib packaging without coordination and a proper release! Thank! |