Sun Sep 17 23:40:06 2023 UTC ()
fixes.xml: correct a file reference


(gutteridge)
diff -r1.193 -r1.194 pkgsrc/doc/guide/files/fixes.xml

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

--- pkgsrc/doc/guide/files/fixes.xml 2023/09/16 18:20:12 1.193
+++ pkgsrc/doc/guide/files/fixes.xml 2023/09/17 23:40:06 1.194
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: fixes.xml,v 1.193 2023/09/16 18:20:12 gutteridge Exp $ --> 1<!-- $NetBSD: fixes.xml,v 1.194 2023/09/17 23:40:06 gutteridge 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
@@ -1598,27 +1598,27 @@ gnu++03, gnu++11, gnu++14, gnu++17, gnu+ @@ -1598,27 +1598,27 @@ gnu++03, gnu++11, gnu++14, gnu++17, gnu+
1598 <filename>bash</filename> to <varname>USE_TOOLS</varname>.</para> 1598 <filename>bash</filename> to <varname>USE_TOOLS</varname>.</para>
1599 </sect2> 1599 </sect2>
1600 1600
1601 <sect2 id="other-programming-languages"> 1601 <sect2 id="other-programming-languages">
1602 <title>Other programming languages</title> 1602 <title>Other programming languages</title>
1603 1603
1604 <para>There are further similar REPLACE variables available, e.g., 1604 <para>There are further similar REPLACE variables available, e.g.,
1605 <varname>REPLACE_AWK</varname> for packages containing awk scripts, 1605 <varname>REPLACE_AWK</varname> for packages containing awk scripts,
1606 and <varname>REPLACE_R</varname> for R. These two, like the others 1606 and <varname>REPLACE_R</varname> for R. These two, like the others
1607 noted above, have their actions defined centrally in 1607 noted above, have their actions defined centrally in
1608 <filename>mk/configure/replace-interpreter.mk</filename>. Other 1608 <filename>mk/configure/replace-interpreter.mk</filename>. Other
1609 languages define the actions of these variables within their own 1609 languages define the actions of these variables within their own
1610 dedicated part of the tree, e.g., <varname>REPLACE_PHP</varname> is 1610 dedicated part of the tree, e.g., <varname>REPLACE_PHP</varname> is
1611 actioned in <filename>lang/php/phpversion.mk</filename>, and 1611 actioned in <filename>lang/php/replace.mk</filename>, and
1612 <varname>REPLACE_PYTHON</varname> is actioned in 1612 <varname>REPLACE_PYTHON</varname> is actioned in
1613 <filename>lang/python/application.mk</filename>. For other languages, 1613 <filename>lang/python/application.mk</filename>. For other languages,
1614 consult the mk files found within their specific directories (the 1614 consult the mk files found within their specific directories (the
1615 naming convention varies), or check the list found in 1615 naming convention varies), or check the list found in
1616 <xref linkend="help-topics" />.</para> 1616 <xref linkend="help-topics" />.</para>
1617 1617
1618 <para>Currently, special handling for other languages varies 1618 <para>Currently, special handling for other languages varies
1619 in pkgsrc. If a compiler package provides a 1619 in pkgsrc. If a compiler package provides a
1620 <filename>buildlink3.mk</filename> file, include that, otherwise 1620 <filename>buildlink3.mk</filename> file, include that, otherwise
1621 just add a (build) dependency on the appropriate compiler 1621 just add a (build) dependency on the appropriate compiler
1622 package.</para> 1622 package.</para>
1623 </sect2> 1623 </sect2>
1624</sect1> 1624</sect1>