peter karlsson <[EMAIL PROTECTED]> cum veritate scripsit:
> > That sounds like a bad news, a potential sign of upstream changing
> > binary interface between 0.1.0 and 0.2.0
>
> I don't know...
The upstream may "fix the package slightly" to make
binary-incompatible change to the library, and call it
0.3.0 (well, it's only natural).
However, in the library sense, if it is binary-incompatible,
it should have a new soname, i.e. 1.0.0
regards,
junichi
--
[EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
