>> On 11/22/2016 08:16 PM, Ned Deily wrote: >> > On Nov 22, 2016, at 11:06, Xavier de Gaye <xdeg...@gmail.com> wrote: >> >> The configure file on the default and 3.6 branches have been generated >> >> with autoconf 2.70 once again. This is annoying when you have to >> >> maintain patches to this configure file in order to build on a non >> >> supported platform. >> > >> > Perhaps another solution to the problem might be to not include the >> autoconf-generated changes in the patches and just always run autoconf >> before doing a build? That's what we suggest for patches >> submitted to the tracker.
On 23 November 2016 at 22:49, Gregory P. Smith <g...@krypto.org> wrote: > The solution to your problem is to maintain your patches _only_ against > configure.ac and rerun autoconf using whatever version you need yourself. Would this solution (forget about regerating the files until build time) be enough Xavier? FWIW I make heavy use of the Mercurial interactive patch mode. I use it to filter out any unnecessary generated changes, while selecting other generated changes relevant to a patch. I.e. hg commit --interactive hg qrefresh --interactive _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
