-
Show log
Commit
-
Hash : e94c0186
Author :
Date : 2017-08-31T14:42:13
build: Rename "Makefile.inc" Makefile fragments to "local.mk" This is done to follow a convention used by a lot of GNU packages. * bin/Makefile.inc: Rename to ... * bin/local.mk: ... this. * doc/Makefile.inc: Rename to ... * doc/local.mk: ... this. * lib/Automake/Makefile.inc: Rename to ... * lib/Automake/local.mk: ... this. * lib/am/Makefile.inc: Rename to ... * lib/am/local.mk: ... this. * lib/Makefile.inc: Rename to ... * lib/local.mk: ... this. * m4/Makefile.inc: Rename to ... * m4/local.mk: ... this. * contrib/t/Makefile.inc: Rename to ... * contrib/t/local.mk: ... this. * t/Makefile.inc: Rename to ... * t/local.mk: ... this. Adapt. * Makefile.am: Adapt.
-
Properties
-
README
-
This is the 'contrib' directory of the GNU Automake distribution. Here you'll find additions to the Automake base distribution, in form of makefile fragments, m4 macros, scripts, documentation, et cetera. Such addition that might be useful for a significant percentage of its general audience, but (for one reason or another) are not deemed appropriate for inclusion into the Automake core. There are several reasons for which a feature can be kept in contrib: 1. The long-term usefulness of the feature is debatable and uncertain; on-field and real-word testing are necessary to prove or disprove its usefulness, before the feature can be committed into the Automake core (as doing so too early would later force us to continue the support for backward-compatibility, even if the features proves flawed or fails to attract widespread use). 2. The APIs or overall design of the feature are still unstable, and need on-field testing to iron warts and usability bugs, or uncover potential flaws. 3. The feature was an historical one, mostly obsoleted but still used "here and there" in the wild; so we want to to deprecate it and remove it from the Automake core, but cannot remove it altogether, for the sake of those still-existing usage. So it gets moved in contrib.