-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torsten Werner wrote: > How do I find out if the API has changed in a new upstream version?
Well, that is never easy, also not with C libraries if upstream is clueless. If you are lucky, upstream is responsible enough to document it. Otherwise it may be necessary to read the code... There are also two kinds of API change to keep track of: (1) backwards-compatible API extension, and (2) an API-breaking change. An extension does not necessitate a new API version, it can be handled in build-deps by versioned dependency for packages that need the extended API. An API breakage, on the other hand, would require a new package name. Cheers, Marcus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkp13l8ACgkQXjXn6TzcAQkcvwCguqT44P6jMdCOfdgag+khadAY 7r0AoNEVQp65/ulH1mVOJTlU54pcPqEj =4cUc -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
