On 10/21/26 11:52, Kamila Szewczyk wrote:
Dear Ariel,
This makes sense. Overall, I think that it's not worth it to stick to
the release-less process, at least as long as GNU config is a separate
project. Perhaps major-minor releases would make sense (to cover two
common patch classes; breaking and keeping backwards compatibility...).
By that logic there should never be a major release "2": the
config.guess and config.sub scripts are meant to be "drop in" updates
for existing packages to add support for new platforms.
A few years ago, there were a few reports to the list about efforts to
build cdparanoia on (IIRC) Raspberry Pi boards; the packaged
config.{guess,sub} scripts predated the ARM64 architecture, but simply
dropping in current versions was enough to make the program build (and I
believe) work.
That is an impressive success for Autoconf: a package successfully
ported to a new CPU architecture with no code changes.
-- Jacob
