Re: Library packages: co-installability, build-depends, transitions

[Ludovic Claude <ludovic.claude@laposte.net>]

I have recently packaged the clirr tool which does exactly that: give it
2 versions of a jar, and it will report any API breaking changes.

Ludovic


Marcus Better a écrit :
> 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
>