For better or worse, although I gather the latter, security/p5-Crypt-SSLeay went interactive some time ago, and the issue is independent of running "portupgrade -fprv security/p5-Crypt-SSLeay" or "make -C /usr/ports/security/p5-Crypt-SSLeay build". Here's an example: ================================================================================ Output from '/usr/ports/workdirs/usr/ports/security/p5-Crypt-SSLeay/work/Crypt-SSLeay-0.72/openssl-version': OpenSSL 1.0.2a 19 Mar 2015 1000201f ================================================================================ The test suite can attempt to connect to public servers to ensure that the code is working properly. If you are behind a strict firewall or have no network connectivity, these tests may fail (through no fault of the code). Do you want to run the live tests (y/N)? [N] The build sits idle waiting for me to hit the enter key. Sure, this could be avoided by setting BATCH=yes in the environment, I haven't tried, but I guess that workaround is more the exception than the rule. Maybe I'm wrong. Any thoughts?
A commit references this bug: Author: mat Date: Mon Apr 27 15:35:43 UTC 2015 New revision: 384857 URL: https://svnweb.freebsd.org/changeset/ports/384857 Log: Make non-interactive. PR: 199354 Sponsored by: Absolight Changes: head/security/p5-Crypt-SSLeay/Makefile