Sat Jul 16 14:28:49 2016 UTC ()
Spelling fix; "opposed" only has two 'o's, not three.


(jakllsch)
diff -r1.143 -r1.144 pkgsrc/doc/guide/files/fixes.xml

cvs diff -r1.143 -r1.144 pkgsrc/doc/guide/files/fixes.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/fixes.xml 2016/07/14 14:39:24 1.143
+++ pkgsrc/doc/guide/files/fixes.xml 2016/07/16 14:28:49 1.144
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: fixes.xml,v 1.143 2016/07/14 14:39:24 leot Exp $ --> 1<!-- $NetBSD: fixes.xml,v 1.144 2016/07/16 14:28:49 jakllsch Exp $ -->
2 2
3<chapter id="fixes"> <?dbhtml filename="fixes.html"?> 3<chapter id="fixes"> <?dbhtml filename="fixes.html"?>
4<title>Making your package work</title> 4<title>Making your package work</title>
5 5
6<sect1 id="general-operation"> 6<sect1 id="general-operation">
7 <title>General operation</title> 7 <title>General operation</title>
8 8
9 <para>One appealing feature of pkgsrc is that it runs on many 9 <para>One appealing feature of pkgsrc is that it runs on many
10 different platforms. As a result, it is important to ensure, 10 different platforms. As a result, it is important to ensure,
11 where possible, that packages in pkgsrc are portable. This 11 where possible, that packages in pkgsrc are portable. This
12 chapter mentions some particular details you should pay 12 chapter mentions some particular details you should pay
13 attention to while working on pkgsrc.</para> 13 attention to while working on pkgsrc.</para>
14 14
@@ -459,27 +459,27 @@ CONFLICTS= bar-[0-9]* @@ -459,27 +459,27 @@ CONFLICTS= bar-[0-9]*
459 <title>Packages that cannot or should not be built</title> 459 <title>Packages that cannot or should not be built</title>
460 460
461 <para>There are several reasons why a package might be 461 <para>There are several reasons why a package might be
462 instructed to not build under certain circumstances. If the 462 instructed to not build under certain circumstances. If the
463 package builds and runs on most platforms, the exceptions 463 package builds and runs on most platforms, the exceptions
464 should be noted with <varname>BROKEN_ON_PLATFORM</varname>. If 464 should be noted with <varname>BROKEN_ON_PLATFORM</varname>. If
465 the package builds and runs on a small handful of platforms, 465 the package builds and runs on a small handful of platforms,
466 set <varname>BROKEN_EXCEPT_ON_PLATFORM</varname> instead. 466 set <varname>BROKEN_EXCEPT_ON_PLATFORM</varname> instead.
467 Both <varname>BROKEN_ON_PLATFORM</varname> and 467 Both <varname>BROKEN_ON_PLATFORM</varname> and
468 <varname>BROKEN_EXCEPT_ON_PLATFORM</varname> are OS triples 468 <varname>BROKEN_EXCEPT_ON_PLATFORM</varname> are OS triples
469 (OS-version-platform) that can use glob-style 469 (OS-version-platform) that can use glob-style
470 wildcards.</para> 470 wildcards.</para>
471 <para>If a package is not appropriate for some platforms (as 471 <para>If a package is not appropriate for some platforms (as
472 oopposed to merely broken), a different set of variables should be 472 opposed to merely broken), a different set of variables should be
473 used as this affects failure reporting and statistics. 473 used as this affects failure reporting and statistics.
474 If the package is appropriate for most platforms, the exceptions 474 If the package is appropriate for most platforms, the exceptions
475 should be noted with <varname>NOT_FOR_PLATFORM</varname>. If 475 should be noted with <varname>NOT_FOR_PLATFORM</varname>. If
476 the package is appropriate for only a small handful of platforms 476 the package is appropriate for only a small handful of platforms
477 (often exactly one), set <varname>ONLY_FOR_PLATFORM</varname> instead. 477 (often exactly one), set <varname>ONLY_FOR_PLATFORM</varname> instead.
478 Both <varname>ONLY_FOR_PLATFORM</varname> and 478 Both <varname>ONLY_FOR_PLATFORM</varname> and
479 <varname>NOT_FOR_PLATFORM</varname> are OS triples 479 <varname>NOT_FOR_PLATFORM</varname> are OS triples
480 (OS-version-platform) that can use glob-style 480 (OS-version-platform) that can use glob-style
481 wildcards.</para> 481 wildcards.</para>
482 <para>Some packages are tightly bound to a specific version of an 482 <para>Some packages are tightly bound to a specific version of an
483 operating system, e.g. LKMs or <filename 483 operating system, e.g. LKMs or <filename
484 role="pkg">sysutils/lsof</filename>. Such binary packages are not 484 role="pkg">sysutils/lsof</filename>. Such binary packages are not
485 backwards compatible with other versions of the OS, and should be 485 backwards compatible with other versions of the OS, and should be