[Python-Dev] Bumping autoconf from 2.68 to 2.69 (original) (raw)
Matthias Klose doko at ubuntu.com
Thu Oct 18 00:07:16 CEST 2012
- Previous message: [Python-Dev] Bumping autoconf from 2.68 to 2.69
- Next message: [Python-Dev] Bumping autoconf from 2.68 to 2.69
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 16.10.2012 17:58, David Malcolm wrote:
On Tue, 2012-10-16 at 10:59 +0200, Stefan Krah wrote:
Charles-François Natali <neologix at free.fr> wrote:
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.
It should be sufficient to install autoconf-x.y into /home/user/bin or something similar. Installing autoconf from source really takes about 3 minutes. FWIW this was also documented in the devguide, as of: http://hg.python.org/devguide/rev/5432be4d4e1a though that description was then removed in: http://hg.python.org/devguide/rev/27be97280cf
so maybe this could be restored.
the python configure.ac doesn't use that internal and specific autoconf features, so it might be ok to live with the diffs. I didn't see any issues using the system supplied autoconf with any python version on not that recent distro releases.
However the effort to use a specific autoconf version for each branch should be minimal (other projects do require this).
Matthias
- Previous message: [Python-Dev] Bumping autoconf from 2.68 to 2.69
- Next message: [Python-Dev] Bumping autoconf from 2.68 to 2.69
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]