[Pkg-alsa-devel] 1.0.13

Jordi Mallach jordi at debian.org
Tue Oct 3 23:20:26 UTC 2006


On Tue, Oct 03, 2006 at 08:44:15PM +0200, Elimar Riesebieter wrote:
> > Elimar, we shouldn't be bumping libasound2-dev requirements if it's not
> > necessary. ditto for the shlibs in alsa-lib. Everytime we bump them
> > without need, it makes other packages transitioning to etch have to wait
> > for alsa-lib.
> How can one check whether it is needed or not?

For build-depends, I just check what the packages require, in
configure.in:

AM_PATH_ALSA(1.0.12)

For shlibs, I dump the objects I'm interested in into a file, then
upgrade, then dump again, and diff:

nm -D /usr/lib/libasound.so.2.0.0 |grep " T " |cut -d " " -f 3- |sort > /tmp/alsa1

[ upgrade libasound2 here ]

nm -D /usr/lib/libasound.so.2.0.0 |grep " T " |cut -d " " -f 3- |sort > /tmp/alsa2

diff alsa1 alsa2.

If there are added symbols, there are API additions and we need a shlibs
bump.

If there are public API removals, we're in trouble, as the API/ABI has
been broken and technically, the soname should have been bumped.

Jordi
-- 
Jordi Mallach Pérez  --  Debian developer     http://www.debian.org/
jordi at sindominio.net     jordi at debian.org     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-alsa-devel/attachments/20061004/585f7759/attachment.pgp


More information about the Pkg-alsa-devel mailing list