Hello,

Wouldn't it be nice if Autoconf had API versioning like
Automake now does?  My understanding is that recent Autoconf
releases have tended to be largely compatible with each
other, but there is no actual guarantee that one Autoconf
version cannot be incompatible with another in minor ways.

Currently very loosely speaking there seems to be the old
Autoconf 2.13 "API" and the newer Autoconf 2.5x "API".  How
about doing what the Automake maintainers do now and have an
APIVERSION which only changes when the API does?  This would
require some change to the current version number system I
suppose but would result in everyone knowing where they were
in terms of Autoconf backward compatibility.

Does this not sound attractive?

Jens


Reply via email to