Log message:
Drop support for TOOLS_DEPMETHOD.<tool>.  The new way to specify a
run-time dependency (DEPENDS) on a tool is to append a ":run" modifier
to the tool name, e.g.,

	USE_TOOLS+=	perl:run

Tools without modifiers or with an explicit ":build" modifier will
cause build dependencies (BUILD_DEPENDS) on those tools to be added.
This makes the notation a bit more compact.

Log message:
Update to 1.9.6:

Bugs fixed in 1.9.6:

* Longstanding bugs:

  - Correctly diagnose `#' comments following trailing backslash.

  - Preserve backslashes preceding `##' lines.

  - Preserve the order of items conditionally appended (+=) to variables.

  - Fix support of installation directory names with spaces on systems
    where mkinstalldirs cannot use `mkdir -p'.

  - Avoid infinite loop in mdate-sh when TIME_STYLE is set.

  - Do not output two definitions of SOURCES (an internal variable).
    One was not formatted and could exceed the maximum line length of
    some third-party tools (e.g., AIX 5.1 grep, breaking dependency
    tracking).

  - Do not empty info files when attempting to rebuild them without makeinfo.

  - Be smarter when a Makefile.am references files in both "./dir" and
    "dir": do not output two rules to create these directories.
    (PR/461)

  - Do not attempt to recover a missing *.elc file if it cannot be
    created because emacs does not exist.

  - Several aclocal fixes for issues occuring when configure.ac
    includes some other m4 files explicitely with m4_include or m4_sinclude.
    (PR/450)

  - depcomp's cpp mode now understands preprocessors that output either
    `#line 42 file' or `# 42 file'.  (Only the latter was supported.)

* Other miscellaneous changes:

  - Update the GPL, and the FSF postal address.

  - Anticipate for python2.5 in AM_PATH_PYTHON.

  - The manual should now compile without any warning from TeX.

Log message:
Remove explicit dependencies on the GNU m4 package with USE_TOOLS+=m4
and appropriate TOOLS_DEPMETHOD.gm4 settings.

Log message:
For packages that use GNU configure, don't bother adding "TOOL"
variables into CONFIGURE_ENV if the new tools framework already takes
care of adding them automatically.

Log message:
Change references to M4 & YACC into TOOLS_M4 & TOOLS_YACC to simplify
transition to new tools framework.

Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.

Log message:
Add RMD160 digests.

Log message:
Update to 1.9.5:

Bugs fixed in 1.9.5:

* Longstanding bugs:

  - All m4 files have been relicensed under an all-permissive license.

    Previously they used a GPL license, and an all-permissive license
    was prepended when they were copied into aclocal.m4, leading to
    some confusion.

  - aclocal now recognizes AU_ALIAS.

  - Improve support for `make -k', it didn't work on cygwin.

  - Fix the definition of FCLINK for preprocessed Fortran.

  - Fixes for auxiliary scripts:

    - depcomp's tru64 mode did not work while compiling libtool libraries
      with static libraries disabled.

    - mdate-sh now copes with Darwin's non-standard ls output.

    - missing properly emulates makeinfo when neither -o nor
      @setfilename are used.

  - Don't output long variable definitions.  Automake normally tries
    to output variable definitions as they are input, bug very long
    lines in Makefile.in can break some sed and make implementations
    with a limited line length.  If a line in a variable definition is
    longer than 1000 characters, automake will wrap the definition
    around 80 columns.  Other definitions are still output untouched.

* Noteworthy manual updates:

  - Hard-Coded Install Paths: New FAQ entry.

  - How the Linker is Chosen: Rewritten.

Log message:
Update to 1.9.4.

Bugs fixed in 1.9.4:

* Longstanding bugs:

  - Portability nits in install-sh and mdata-sh.

  - Don't let `make install' fails if a _JAVA primary becomes empty
    because of conditionals.

  - Do not confuse CHANGELOG with ChangeLog on case-insensitive
    case-preserving file systems (likewise for all automatically
    distributed files).

  - Do not embed $DESTDIR in Python's byte-code files.

  - Work around programs that read stdin when checking for --version
    and --help options (when the `std-options' is used).

  - Fix AM_PATH_PYTHON to correctly define PYTHON as `:' when no minimum
    version was supplied and no interpreter is found.

* Noteworthy manual updates:

  - Conditional Subdirectories: more comments about non-distributed
    subdirectories.

  - Flag Variables Ordering: new FAQ entry.

  - Per-Object Flags: new FAQ entry.

Log message:
Update to 1.9.3:

Bugs fixed in 1.9.3:

* Bug introduced by 1.9:

  - Dependency tracking using mode "dashmstdout" or \ 
"dashXmstdout" did
    not work for libtool objects compiled with --tag (i.e., compiled
    with Libtool 1.5 or later).  The compilation would succeed, but
    `depcomp' would emit a warning and not output any dependency
    information.

* Long standing bugs:

  - Ignore comments from augmented variables, so that
       FOO = foo # bar
       FOO += baz
    no longer results in `FOO = foo # bar baz'.

  - `install-sh -d a/b/' failed to create `a/b/' because of the trailing `/'.

  - _PROGRAMS now always create programs.  Before 1.9 it would
    mistakenly create a libtool library if the name of the program
    ended in `.la'.  Between 1.9 and 1.9.2 a program with such a name
    would fail to build because half the code was assuming a program
    was being built, while the other half was considering a library...

  - `compile' now handles `*.obj' objects.

  - `aclocal' recognizes AC_DEFUN_ONCE.

* Noteworthy manual updates:

  - LIBOBJS: more documentation and an example setup.
  - Libtool Convenience Libraries: show how to force the linker selection.
  - Extending: more comments about install-data-hook vs install-exec-hook.
  - Clean: document -local targets.