As autoconf-archive installs the same ax_*.m4 macros that gnome-common
installs, which are copied from autoconf-archive into gnome-common, add
a configure argument to toggle autoconf-archive support.

Passing --without-autoconf-archive to configure (or not providing an
argument) disables compatibility (parallel-installability) with
autoconf-archive, and installs the ax_*.m4 macros. If
--with-autoconf-archive is passed to configure, the macros are not
installed, and gnome-common will not install any M4 macros that conflict
with autoconf-archive.

https://bugzilla.gnome.org/show_bug.cgi?id=747920

https://bugzilla.gnome.org/show_bug.cgi?id=748394

Just as for GNOME_COMPILE_WARNINGS, GNOME_CXX_WARNINGS has been
deprecated in favour of AX_COMPILER_FLAGS. See commit
b57bae0b for details.

https://bugzilla.gnome.org/show_bug.cgi?id=729406

Use AX_COMPILER_FLAGS instead, which comes from the autoconf-archive. It
supports more compilers than just GCC, has a wider selection of flags,
supports LDFLAGS, and is maintained for more projects than just GNOME.

GNOME_COMPILE_WARNINGS has not been ported to AX_COMPILER_FLAGS as:
 • the default argument is a little difficult to map to
   AX_COMPILER_FLAGS’ IS-RELEASE argument; and
 • AX_COMPILER_FLAGS depends on some other macros in autoconf-archive
   licenced as GPLv3, which would potentially be tricky to copy into
   gnome-common.

The --enable-iso-c argument is deprecated as well. Projects should
choose which C standard they want to use, and hard-code that in their
compiler flags. It is not something which should be set by the
developer.

GNOME_CXX_WARNINGS is not deprecated, but may be in future.

No further changes should be made to GNOME_COMPILE_WARNINGS: please make
them to AX_COMPILER_FLAGS instead.

https://bugzilla.gnome.org/show_bug.cgi?id=729407

Not setting $srcdir will lead to broken out-of-tree autogen call, so
let's ask to set it

https://bugzilla.gnome.org/show_bug.cgi?id=741891

Well, many people still use deprecated variables for 10y, maybe
it's time to let them know.

https://bugzilla.gnome.org/show_bug.cgi?id=741891

Let's not repeat ourself in autogen.sh, there are already many places
with the package name.

https://bugzilla.gnome.org/show_bug.cgi?id=741891

It's usually not required, so let's not show a bad example

https://bugzilla.gnome.org/show_bug.cgi?id=741891

Function return type mismatch should be considered broken, as it can cause
unexpected result or compilation error.

https://bugzilla.gnome.org/show_bug.cgi?id=741558

Remove support for checking for the GNOME_DOC_INIT macro in configure.ac
and calling gnome-doc-prepare if found. gnome-doc-utils has not been
used in any modules we care about for a long time.

https://bugzilla.gnome.org/show_bug.cgi?id=729931

This pertained to the old GNOME documentation infrastructure, used
before Mallard existed. This isn’t used by any modules we care about
any more. Most modules which set USE_COMMON_DOC_BUILD do so erroneously.

https://bugzilla.gnome.org/show_bug.cgi?id=729931

It’s been deprecated for a while, and apparently no modules (which I
have checked out, at least) still use it.

https://bugzilla.gnome.org/show_bug.cgi?id=735416

Now that the macros have been committed upstream, we can link to their
manual pages rather than the bug reports.

And request that appstream-xml.m4 get installed if missing.

https://bugzilla.gnome.org/show_bug.cgi?id=736497

The autoconf-archive AX_CODE_COVERAGE macro should be used instead.

https://bugzilla.gnome.org/show_bug.cgi?id=729405

The modules which it deprecates are all ancient and unused. Many of the
modules which use GNOME_MAINTAINER_MODE_DEFINES don’t make use of the
DISABLE_DEPRECATED variable it generates anyway.

If a module really wants maintainer mode, they should use
AM_MAINTAINER_MODE. Otherwise, they should just eliminate this call
entirely.

https://bugzilla.gnome.org/show_bug.cgi?id=735417

The autoconf-archive AX_DEBUG_CHECK macro should be used instead, or the
macro contents should just be substituted into configure.ac directly,
since it’s so simple.

https://bugzilla.gnome.org/show_bug.cgi?id=729403

https://bugzilla.gnome.org/show_bug.cgi?id=735418

Some projects want to see no warnings at all, for example, projects that
are written in Vala. But GNOME_COMPILE_WARNINGS([no]) is a no-op that
does nothing to turn off the default compiler warnings. Presumably if
you ask for no compiler warnings, you want no compiler warnings, so
suppress them in this case instead.

https://bugzilla.gnome.org/show_bug.cgi?id=734973

https://bugzilla.gnome.org/show_bug.cgi?id=732988

It was completely outdated and unused. The REQUIRED_M4MACROS
infrastructure is, however, still in use.

https://bugzilla.gnome.org/show_bug.cgi?id=729932

https://bugzilla.gnome.org/show_bug.cgi?id=729410

We don’t like references to CVS any more. Update the guidelines to no
longer reference GNOME_COMMON_INIT.

https://bugzilla.gnome.org/show_bug.cgi?id=729410

Otherwise we may end up overriding what was manually set in the
environment.

Volker Sobek authored Mar 22, 2014 and Colin Walters committed Mar 22, 2014

Commit 7f977b02 introduced a check if stdin is ins't a tty, and
prevent printing terminal codes in this case. But the check was wrong
and always failed.

https://bugzilla.gnome.org/show_bug.cgi?id=726892

This is the version of automake that introduced ACLOCAL_PATH support, so
make sure that we have it before attempting to configure the package.

jhbuild has set this variable for more than two years.

https://bugzilla.gnome.org/show_bug.cgi?id=726208

Due to a likely copy-paste mistake, the default value of IFS was being
set to 9 spaces instead of a tab and a space.  Fix that.

https://bugzilla.gnome.org/show_bug.cgi?id=726208