Jamie Wilkinson <[EMAIL PROTECTED]> cum veritate scripsit: > So, as I understand it, there's an _incompatible_ API change (and thus > requiring a SONAME change) when: > > * function prototypes (incl names) that are exported are changed or obsoleted > * structs change or are obsoleted > > I think I can see a way to check for both cases, given the old and new > library and header file... I'll keep you posted.
Generally, if a non-comment portion of a header file changes, it would be almost safe to assume that the interface has changed. There could, however, be changes in the source which does affect. I don't know if there could be a systematic way to do it. Warning might be possible, but not strict and real checking. Lintian won't be able to do this, because lintian only has access to one version of source at the time. -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
