[Python-Dev] Bumping autoconf from 2.68 to 2.69 (original) (raw)

Petri Lehtinen petri at digip.org
Tue Oct 16 11:53:55 CEST 2012

Trent Nelson wrote:

> build breaking is another matter, of course. If we are > going to mandate a specific version again, that should be documented and > checked for.

My preference: bump to 2.69 and set ACPREREQ(2.69). If 2.69 proves unworkable, revert back to 2.68 and ACPREREQ(2.68). I definitely like the idea of explicitly setting the version being used via ACPREREQ, as this will prevent accidental version churn being checked in by a committer inadvertently.

Bear in mind that AC_PREREQ sets the minimum required version. It cannot be used to prevent from running newer autoconf in the future.

Petri

More information about the Python-Dev mailing list