build: check-manifest runs after tests

And just treat it as a non-fatal nag when checking the rest of the
codebase.  Calling it "check-manifest" as a `make' target
preserves the old behavior, which causes the check to fail
if a file were added to the worktree without changing the
MANIFEST.

diff --git a/Makefile.PL b/Makefile.PL
index 30b8adda2f0166126a543ba0b9cd42367a155e49..472baa9b080eda0466dd099be9bdc2b5eebcf4f2 100644 (file)
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -180,18 +180,22 @@ syntax:: \$(my_syntax)
 changed = \$(shell git ls-files -m)
 dsyn :: \$(addsuffix .syntax, \$(filter \$(changed), \$(syn_files)))
 
-check-manifest :: MANIFEST
-       if test -e .git && git ls-files >\$?.gen 2>&1; then \\
-               diff -u \$? \$?.gen; fi
+check_manifest := if test -e .git && git ls-files >MANIFEST.gen 2>&1; then \\
+               diff -u MANIFEST MANIFEST.gen; fi
+
+check-manifest : MANIFEST
+       \$(check_manifest)
 
 # the traditional way running per-*.t processes:
-check-each :: pure_all check-manifest
+check-each :: pure_all
        \$(EATMYDATA) \$(PROVE) --state=save -bvw -j\$(N)
+       -@\$(check_manifest)
 
 # lightly-tested way to run tests, relies "--state=save" in check-each
 # for best performance
-check-run :: pure_all check-manifest
+check-run :: pure_all
        \$(EATMYDATA) \$(PROVE) -bvw t/run.perl :: -j\$(N)
+       -@\$(check_manifest)
 
 check :: check-each