Versions in ports
aszostak at partner.eso.org
Wed Sep 16 02:17:39 PDT 2015
>>>> And their newer versions are not backwards compatible with C 1.0, thus:
>>> what is the nature of this incompatibility?
>> Two examples that I can think of that affect the kind of software I work with are:
>> 1) The internal algorithm of some API functions have changed, even though the
>> API interface has not. This might lead to different results for certain invocations
>> of these functions.
> this would be a bug in that software
I disagree. There is a large body of software that changes its internal algorithms without changing the API. First obvious examples would be math libraries, BLAS and other linear algebra libraries. Just because the internal algorithm changed, does not make it a bug as long as library version numbers are updated appropriately.
>> 2) The command line interface for certain programs has changed, which are used
>> under the hood by higher level tools.
> and this also if the command line interface was meant to be an interface to other programs
Again I disagree. Why would it be a bug to add CLI options to a program and bump its version number? More or less the same rules could apply as is used for library versioning.
More information about the macports-users