aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorbdrewery <bdrewery@FreeBSD.org>2014-05-31 00:40:33 +0800
committerbdrewery <bdrewery@FreeBSD.org>2014-05-31 00:40:33 +0800
commitec79adaae069f6744ae60d718dc30b91068caf6f (patch)
treefd829e6d45d1f34ef10d77fb5ef7f5999d482364
parente1a71ba137b8968ac83e46276150ff1ed2ef5fc9 (diff)
downloadfreebsd-ports-gnome-ec79adaae069f6744ae60d718dc30b91068caf6f.tar.gz
freebsd-ports-gnome-ec79adaae069f6744ae60d718dc30b91068caf6f.tar.zst
freebsd-ports-gnome-ec79adaae069f6744ae60d718dc30b91068caf6f.zip
- When showing vulnerability warning give an explanation that there
will not necessarily be an update. Give advice on how to skip the check. It is the user's choice afterall. With hat: portmgr Reported by: jhb
-rw-r--r--Mk/bsd.port.mk2
1 files changed, 2 insertions, 0 deletions
diff --git a/Mk/bsd.port.mk b/Mk/bsd.port.mk
index 30eb3ff1f56f..8ad0638b6e80 100644
--- a/Mk/bsd.port.mk
+++ b/Mk/bsd.port.mk
@@ -3325,6 +3325,8 @@ check-vulnerable:
${ECHO_MSG} "===> ${PKGNAME} has known vulnerabilities:"; \
${ECHO_MSG} "$$vlist"; \
${ECHO_MSG} "=> Please update your ports tree and try again."; \
+ ${ECHO_MSG} "=> Ports are marked vulnerable regardless of their being an update available."; \
+ ${ECHO_MSG} "=> If you wish to ignore this vulnerability rebuild with 'make DISABLE_VULNERABILITIES=yes'"; \
exit 1; \
fi; \
fi