GNOME Bugzilla – Bug 598768
Use recommended autoconf input name: `configure.ac'
Last modified: 2010-05-07 08:09:58 UTC
Created attachment 145665 [details] [review] 0001-Rename-configure.in-to-configure.ac.patch In the autoconf manual [1] the name `configure.ac' is promoted and `configure.in' is considered legacy. The attached patch renames configure.in to configure.ac and changes references to the file accordingly. It also does some whitespace cleanup so that the patch can be applied without git complaining. [1] http://www.gnu.org/software/autoconf/manual/autoconf.html#Writing-Autoconf-Input
Forgot to say that I'm ready to push this as soon as I get an OK.
One thing this will break is automatic reconfigure when running make after switching between master and a branch that still uses configure.in (or on master while bisecting over this change).
Is there any practical advantage?
Oops I must have missed the last bugzilla mail The practical advantage is that GTK+ will have the Autoconf input name that developers expect. As time passes, more and more will expect the name to be configure.ac.
As I said on the list the other day, I don't see a big advantage, but I don't mind it. So just go ahead.
Created attachment 157098 [details] [review] Rename configure.in to configure.ac Reworked patch against latest master. Also, use AM_MAINTAINER_MODE([enable]) instead AM_MAINTAINER_MODE because disables dependency-checking for autotools-generated stuff. More info about this here [1] and [2] [1] http://www.gnu.org/software/automake/manual/automake.html#maintainer_002dmode [2] http://mail.gnome.org/archives/desktop-devel-list/2010-February/msg00093.html
Comment on attachment 145665 [details] [review] 0001-Rename-configure.in-to-configure.ac.patch commit ccc53b9a45f35af358d1387a6db14838d6977fd4
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.