[pkgsrc/trunk]: pkgsrc/mk/check mk/check/check-portability: exclude REPLACE_B...

[rillig <rillig%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/1ed4f56eab3a
branches:  trunk
changeset: 424627:1ed4f56eab3a
user:      rillig <rillig%pkgsrc.org@localhost>
date:      Fri Mar 13 06:31:43 2020 +0000

description:
mk/check/check-portability: exclude REPLACE_BASH by default

Since the portability checks are concerned about bashisms, it doesn't make
sense to apply them to programs that will later be run in bash anyway.

Suggested by gdt via private mail.

diffstat:

 mk/check/check-portability.mk |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (30 lines):

diff -r 30ddc47eb042 -r 1ed4f56eab3a mk/check/check-portability.mk
--- a/mk/check/check-portability.mk     Fri Mar 13 06:06:49 2020 +0000
+++ b/mk/check/check-portability.mk     Fri Mar 13 06:31:43 2020 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: check-portability.mk,v 1.11 2020/03/11 19:58:45 rillig Exp $
+# $NetBSD: check-portability.mk,v 1.12 2020/03/13 06:31:43 rillig Exp $
 #
 # This file contains some checks that are applied to the configure
 # scripts to check for certain constructs that are known to cause
@@ -19,7 +19,7 @@
 #      The list of files that should be skipped in the portability
 #      check.
 #
-#      Default value: empty.
+#      Default value: ${REPLACE_BASH}
 #      Example: debian/*
 
 _VARGROUPS+=                   check-portability
@@ -30,9 +30,9 @@
 CHECK_PORTABILITY?=            yes
 .endif
 CHECK_PORTABILITY?=            no
-CHECK_PORTABILITY_SKIP?=       # none
+CHECK_PORTABILITY_SKIP?=       ${REPLACE_BASH}
 
-.if ${CHECK_PORTABILITY:M[Yy][Ee][Ss]} != ""
+.if ${CHECK_PORTABILITY:tl} == yes && ${CHECK_PORTABILITY_SKIP} != "*"
 pre-configure-checks-hook: _check-portability
 .endif
 .PHONY: _check-portability