init.m4: add probe to check "rm -f" without args work
authorStefano Lattarini <stefano.lattarini@gmail.com>
Sat, 12 Jan 2013 18:20:54 +0000 (19:20 +0100)
committerStefano Lattarini <stefano.lattarini@gmail.com>
Wed, 16 Jan 2013 12:11:54 +0000 (13:11 +0100)
commitf78b0f0b2741fcdd4e21151758a8a75ddaa8aa17
tree10ef41ceaf43d29b03ccd9452a87b56f9b4101be
parent593032130119da79aba14dc26c3cc985bf3a5610
init.m4: add probe to check "rm -f" without args work

See automake bug#10828.

POSIX will say in a future version that running "rm -f" with no argument
is OK: <http://austingroupbugs.net/view.php?id=542>).

We want to be able to make that assumption in our Makefile recipes.
So we introduce an aggressive probe to check that the usage we want is
actually supported "in the wild" to an acceptable degree.

* m4/init.m4 (AM_INIT_AUTOMAKE): Implement the probe.  To make any issue
more visible, cause the running configure to be aborted by default if
the 'rm' program in use doesn't match our expectations; the user can
still override this though, by setting the ACCEPT_INFERIOR_RM_PROGRAM
environment variable to "yes".

* t/spy-rm.tap: Update heading comments.
* t/rm-f-probe.sh: New test.
* t/list-of-tests.mk: Add it.
* PLANS/rm-f-without-args.txt: Adjust.

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
PLANS/rm-f-without-args.txt
m4/init.m4
t/list-of-tests.mk
t/rm-f-probe.sh [new file with mode: 0755]
t/spy-rm.tap