aboutsummaryrefslogtreecommitdiff
path: root/configure.ac
diff options
context:
space:
mode:
authorStefano Lattarini <stefano.lattarini@gmail.com>2012-07-19 09:50:01 +0200
committerJunio C Hamano <gitster@pobox.com>2012-07-19 10:30:26 -0700
commitdc7ace5f776f30fe4e10d8a3fa8146ad21893544 (patch)
tree3e9960809dfb4af337f22b13796846d940c6792f /configure.ac
parentac5fc1c57f2a964e1b5480a25b6fd447ab18b9b9 (diff)
downloadgit-dc7ace5f776f30fe4e10d8a3fa8146ad21893544.tar.gz
git-dc7ace5f776f30fe4e10d8a3fa8146ad21893544.tar.xz
build: "make clean" should not remove configure-generated files
Those filed hold variables, settings and information set by the configuration process run by './configure'; in Autotools-based build system that kind of stuff should only be removed by "make distclean". Having it removed by "make clean" is not only inconsistent, but causes real confusion for that part of the Git audience that is used to the Autotools semantics; for example, an autotools old-timer that has run: ./configure --prefix /opt/git in the past, without running "make distclean" afterwards, would expect a "make install" issued after a "make clean" to rebuild and install git in '/opt/git'; but with the current behaviour, the "make clean" invocation removes (among the other things) the file 'config.mak.autogen', so that the "make install" falls back to the default prefix of '$HOME', thus installing git in the user's home directory -- definitely unexpected. Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'configure.ac')
0 files changed, 0 insertions, 0 deletions