IMHO configure should not be rebuilt systematically, not even "on every Huge build". The distributed auto/configure should be good enough for most users, and certainly for me who prefer not even to modify the Makefile (I pass the configure arguments to make by means of environment variables). If the build process _could_ modify a file which is under version control, that could give problems at the next run of git or Mercurial, which would stop in error, telling you you need to commit your changes before you may pull from the remote.
Best regards, Tony. On Sat, Dec 5, 2015 at 2:11 AM, James McCoy <[email protected]> wrote: > I've updated the patch to only rebuild the autoconf files when performing > the "all features enabled" build. The small and tiny builds will use the > configure script from the repo. > > — > Reply to this email directly or view it on GitHub. > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
