Too fast, here's updated patch which matches more pages - not including
translated web pages.
$ gfind . -type f -iname '*.html' ! -regex
'.*/\(cs\|de\|es\|fr\|hu\|nl\|pf\|pl\|pt\|ru\|zh\)/.*' -exec grep -l
'infrastructure/build' {} \; | \
while read file ; do
perl -i -pe 's/infrastructure\/build/infrastructure\/bin/' $file
done
jirib
Index: ports.html
===================================================================
RCS file: /cvs/www/ports.html,v
retrieving revision 1.106
diff -u -p -r1.106 ports.html
--- ports.html 29 Jul 2010 05:29:30 -0000 1.106
+++ ports.html 1 Dec 2010 20:57:23 -0000
@@ -333,14 +333,14 @@ Corrections are always welcome, but in a
</ul>
For ports that don't build correctly, a complete build transcript is almost
always required. You can use the portslogger script, found in
-/usr/ports/infrastructure/build, for this. A sample run of portslogger
+/usr/ports/infrastructure/bin, for this. A sample run of portslogger
might be:
<pre>
% cd /usr/ports/archivers/unzip
% su
# mkdir -p ~/portslogs
- # make clean install 2>&1 |
/usr/ports/infrastructure/build/portslogger \
+ # make clean install 2>&1 |
/usr/ports/infrastructure/bin/portslogger \
~/portslogs
</pre>
Index: porttest.html
===================================================================
RCS file: /cvs/www/porttest.html,v
retrieving revision 1.20
diff -u -p -r1.20 porttest.html
--- porttest.html 20 Dec 2005 08:33:09 -0000 1.20
+++ porttest.html 1 Dec 2010 20:57:23 -0000
@@ -204,7 +204,7 @@
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 <a href=
-
"http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/build/portslogger";>
+
"http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/bin/portslogger";>
portslogger</a> which is like an "intelligent tee" that redirects output
into a log file.</p>
@@ -216,7 +216,7 @@
<tr>
<td nowrap bgcolor="#EEEEEE">
<pre>
- # make install 2>&1 | /usr/ports/infrastructure/build/portslogger .
+ # make install 2>&1 | /usr/ports/infrastructure/bin/portslogger .
</pre>
</td>
</tr>
Index: faq/faq15.html
===================================================================
RCS file: /cvs/www/faq/faq15.html,v
retrieving revision 1.76
diff -u -p -r1.76 faq15.html
--- faq/faq15.html 1 Nov 2010 09:48:45 -0000 1.76
+++ faq/faq15.html 1 Dec 2010 20:57:23 -0000
@@ -1649,13 +1649,13 @@ The more information you provide, the mo
For ports which do not build correctly, a complete build transcript is
almost always required.
You can use the portslogger script, found in
-<tt>/usr/ports/infrastructure/build</tt>, for this.
+<tt>/usr/ports/infrastructure/bin</tt>, for this.
A sample run of portslogger might be:
<blockquote><pre>
$ mkdir ~/portslogs
$ cd /usr/ports/archivers/unzip
-$ make clean install 2>&1 | /usr/ports/infrastructure/build/portslogger
\
+$ make clean install 2>&1 | /usr/ports/infrastructure/bin/portslogger \
~/portslogs
</pre></blockquote>
Index: faq/ports/ports.html
===================================================================
RCS file: /cvs/www/faq/ports/ports.html,v
retrieving revision 1.8
diff -u -p -r1.8 ports.html
--- faq/ports/ports.html 21 Nov 2010 10:26:03 -0000 1.8
+++ faq/ports/ports.html 1 Dec 2010 20:57:23 -0000
@@ -735,14 +735,14 @@ Corrections are always welcome, but in a
</ul>
For ports that don't build correctly, a complete build transcript is almost
always required. You can use the portslogger script, found in
-/usr/ports/infrastructure/build, for this. A sample run of portslogger
+/usr/ports/infrastructure/bin, for this. A sample run of portslogger
might be:
<pre>
% cd /usr/ports/archivers/unzip
% su
# mkdir -p ~/portslogs
- # make clean install 2>&1 |
/usr/ports/infrastructure/build/portslogger \
+ # make clean install 2>&1 |
/usr/ports/infrastructure/bin/portslogger \
~/portslogs
</pre>
Index: faq/ports/testing.html
===================================================================
RCS file: /cvs/www/faq/ports/testing.html,v
retrieving revision 1.6
diff -u -p -r1.6 testing.html
--- faq/ports/testing.html 19 Sep 2010 13:35:40 -0000 1.6
+++ faq/ports/testing.html 1 Dec 2010 20:57:23 -0000
@@ -231,7 +231,7 @@ PERFORMANCE OF THIS DOCUMENTATION
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 <a href=
-
"http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/build/portslogger";>
+
"http://www.openbsd.org/cgi-bin/cvsweb/ports/infrastructure/bin/portslogger";>
portslogger</a> which is like an "intelligent tee" that redirects output
into a log file.</p>
@@ -243,7 +243,7 @@ PERFORMANCE OF THIS DOCUMENTATION
<tr>
<td nowrap bgcolor="#EEEEEE">
<pre>
- # make install 2>&1 | /usr/ports/infrastructure/build/portslogger .
+ # make install 2>&1 | /usr/ports/infrastructure/bin/portslogger .
</pre>
</td>
</tr>
