Hello, just a small update for the port testing guide ;-) Cheers, Alex
Index: testing.html =================================================================== RCS file: /cvs/www/faq/ports/testing.html,v retrieving revision 1.42 diff -u -p -r1.42 testing.html --- testing.html 28 May 2019 01:53:12 -0000 1.42 +++ testing.html 29 Jul 2019 20:08:50 -0000 @@ -260,8 +260,9 @@ Even if the port is working fine comment If we have ten posts where people say that the port runs fine under different architectures then the commit is done faster. If it does not work, then some information must be given. -There are tools that can help in this task, like portslogger(1) which is like -an "intelligent tee" that redirects output into a log file. +There are tools that can help in this task, like +<a href="https://man.openbsd.org/portslogger";>portslogger(1)</a> which is +like an "intelligent tee" that redirects output into a log file. <p> Example:
Index: testing.html =================================================================== RCS file: /cvs/www/faq/ports/testing.html,v retrieving revision 1.42 diff -u -p -r1.42 testing.html --- testing.html 28 May 2019 01:53:12 -0000 1.42 +++ testing.html 29 Jul 2019 20:09:30 -0000 @@ -260,8 +260,9 @@ Even if the port is working fine comment If we have ten posts where people say that the port runs fine under different architectures then the commit is done faster. If it does not work, then some information must be given. -There are tools that can help in this task, like portslogger(1) which is like -an "intelligent tee" that redirects output into a log file. +There are tools that can help in this task, like +<a href="https://man.openbsd.org/portslogger";>portslogger(1)</a> which is +like an "intelligent tee" that redirects output into a log file. <p> Example:
