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

Antoine Pitrou solipsis at pitrou.net
Tue Oct 16 11:27:24 CEST 2012

On Tue, 16 Oct 2012 05:05:23 -0400 Trent Nelson <trent at snakebite.org> wrote:

On Tue, Oct 16, 2012 at 01:43:37AM -0700, Charles-François Natali wrote: > > My understanding is that we use a specific version of autoconf. > > The reason is that otherwise we end up with useless churn in the repo > > as the generated file changes when different committers use different > > versions. In the past we have had issues with a new autoconf version > > actually breaking the Python build, so we also need to test a new version > > before switching to it. > > Well, so I guess all committers will have to use the same > Linux/FreeBSD/whatever distribution then? > AFAICT there's no requirement regarding the mercurial version used by > committers either.

Autoconf is a special case though. Different versions of autoconf produce wildly different outputs for 'configure', making it impossible to vet configure.ac changes by reviewing the configure diff.

Isn't it enough to review the configure.ac diff?

Regards

Antoine.

More information about the Python-Dev mailing list