maint.mk: don't silently disable project-specific syntax-check rules
authorJim Meyering <meyering@redhat.com>
Sat, 3 Apr 2010 16:03:16 +0000 (18:03 +0200)
committerJim Meyering <meyering@redhat.com>
Sat, 3 Apr 2010 16:03:16 +0000 (18:03 +0200)
* top/maint.mk (_prohibit_regexp): Define, to help people realize
that they need to convert their project-specific syntax-check rules
to use the new _sc_search_regexp.

ChangeLog
top/maint.mk

index 3f33302..36443a3 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2010-04-03  Jim Meyering  <meyering@redhat.com>
+
+       maint.mk: don't silently disable project-specific syntax-check rules
+       * top/maint.mk (_prohibit_regexp): Define, to help people realize
+       that they need to convert their project-specific syntax-check rules
+       to use the new _sc_search_regexp.
+
 2010-04-03  Bruno Haible  <bruno@clisp.org>
 
        fchdir: Fix regression introduced on 2010-03-08.
index 13a0438..3038680 100644 (file)
@@ -189,6 +189,15 @@ define _sc_say_and_exit
    { echo -e "$(ME): $$msg" 1>&2; exit 1; };
 endef
 
+# _sc_search_regexp used to be named _prohibit_regexp.  However,
+# upgrading to the new definition and leaving the old name undefined
+# would usually convert each custom rule using $(_prohibit_regexp)
+# (usually defined in cfg.mk) into a no-op.  This definition ensures
+# that people know right away if they're still using the old name.
+# FIXME: remove in 2012.
+_prohibit_regexp = \
+  $(error '*** you need to s/_prohibit_regexp/_sc_search_regexp/, and adapt')
+
 define _sc_search_regexp
    dummy=; : so we do not need a semicolon before each use;            \
                                                                        \