On Sun, Sep 02, 2001 at 04:04:11PM -0400, Steve M. Robbins wrote:
> 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?
>
best solution INHO is to write .shlibs file by hand and update minimum
version required every time you understand ABI is changing. upstream
developer can help a lot in this.
-----[ Domenico Andreoli, aka cavok
--[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
