* Obsolescent features:
- Use of the long-deprecated two- and three-arguments invocation forms
- of the AM_INIT_AUTOMAKE is not documented anymore. It's still
- supported though (albeit with a warning in the 'obsolete' category),
- to cater for people who want to define the version number for their
- package dynamically (e.g., from the current VCS revision). We'll
- have to continue this support until Autoconf itself is fixed to allow
- better support for such dynamic version numbers.
+ of the AM_INIT_AUTOMAKE is no longer documented. It's still supported
+ though (albeit with a warning in the 'obsolete' category), to cater
+ for people who want to define the version number for their package
+ dynamically (e.g., from the current VCS revision). We'll have to
+ continue this support until Autoconf itself is fixed to allow better
+ support for such dynamic version numbers.
* Elisp byte-compilation:
"make V=0" to enable quieter output in the package he's building.
- The 'silent-rules' option has now become a no-op, preserved for
- backward-compatibility only. In particular, its use does not disable
- the warnings in the 'portability-recursive' category anymore.
+ backward-compatibility only. In particular, its use no longer
+ disables the warnings in the 'portability-recursive' category.
* Texinfo Support:
* Automatic remake rules and 'missing' script:
- - The 'missing' script does not try anymore to update the timestamp
- of out-of-date files that require a maintainer-specific tool to be
+ - The 'missing' script no longer tries to update the timestamp of
+ out-of-date files that require a maintainer-specific tool to be
remade, in case the user lacks such a tool (or has a too-old version
of it). It just give a useful warning, and in some cases also a tip
about how to obtain such a tool.