Re: versioned shlibs file -- when and why

["Steve M. Robbins" <steven.robbins@videotron.ca>]

On Sun, Sep 02, 2001 at 01:22:32PM -0500, Steve Langasek wrote:

> Version 2.1.1 of libfoo provides functions foo_open, foo_close.  Version 2.1.2
> of libfoo provides functions foo_open, foo_close, and foo_read.  This doesn't
> break the ABI; foo_open and foo_close have not changed, so there's no need to
> increment the library so number (and thereby change the package name).
> However, a binary compiled against libfoo 2.1.2 that uses foo_read will /not/
> work with libfoo 2.1.1, so you need a version in shlibs.

This suggests that one ought to increase the version in the shlibs file
each time the ABI is changed, but not change it otherwise.

So is "dh_makeshlibs -V" (i.e. bump the version uncondtionally) simply
the lazy-man's way of doing this?

-S

-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants