Mon May 15 21:14:44 2023 UTC ()
pkginstall.xml: fix a typo


(gutteridge)
diff -r1.23 -r1.24 pkgsrc/doc/guide/files/pkginstall.xml
cvs diff -r1.23 -r1.24 pkgsrc/doc/guide/files/pkginstall.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/pkginstall.xml 2023/05/12 07:13:57 1.23
+++ pkgsrc/doc/guide/files/pkginstall.xml 2023/05/15 21:14:43 1.24
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: pkginstall.xml,v 1.23 2023/05/12 07:13:57 dholland Exp $ --> 1<!-- $NetBSD: pkginstall.xml,v 1.24 2023/05/15 21:14:43 gutteridge Exp $ -->
2 2
3<chapter id="pkginstall"> <?dbhtml filename="pkginstall.html"?> 3<chapter id="pkginstall"> <?dbhtml filename="pkginstall.html"?>
4<title>The pkginstall framework</title> 4<title>The pkginstall framework</title>
5 5
6<para>This chapter describes the framework known as 6<para>This chapter describes the framework known as
7<literal>pkginstall</literal>, whose key features are:</para> 7<literal>pkginstall</literal>, whose key features are:</para>
8 8
9<itemizedlist> 9<itemizedlist>
10 10
11 <listitem> 11 <listitem>
12 <para>Generic installation and manipulation of directories and files 12 <para>Generic installation and manipulation of directories and files
13 outside the pkgsrc-handled tree, <varname>LOCALBASE</varname>.</para> 13 outside the pkgsrc-handled tree, <varname>LOCALBASE</varname>.</para>
14 </listitem> 14 </listitem>
@@ -337,27 +337,27 @@ created with OWN_DIRS @@ -337,27 +337,27 @@ created with OWN_DIRS
337known place, you need to teach each package where to install its files. In 337known place, you need to teach each package where to install its files. In
338some cases you will have to patch the package Makefiles to achieve it. If 338some cases you will have to patch the package Makefiles to achieve it. If
339you are lucky, though, it may be as easy as passing an extra flag to the 339you are lucky, though, it may be as easy as passing an extra flag to the
340configuration script. This is the case for packages using GNU 340configuration script. This is the case for packages using GNU
341autoconf:</para> 341autoconf:</para>
342 342
343<programlisting> 343<programlisting>
344CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR} 344CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
345</programlisting> 345</programlisting>
346 346
347<para>Note that this specifies where the package has to <emphasis>look 347<para>Note that this specifies where the package has to <emphasis>look
348for</emphasis> its configuration files, not where they will be installed. 348for</emphasis> its configuration files, not where they will be installed.
349Fortunately, there is a different way to specify the latter, as seen 349Fortunately, there is a different way to specify the latter, as seen
350in the next seection, although the combination is rather confusing at 350in the next section, although the combination is rather confusing at
351first glance.</para> 351first glance.</para>
352 352
353</sect2> 353</sect2>
354 354
355<!-- ================================================================== --> 355<!-- ================================================================== -->
356 356
357<sect2 id="conf-files-patching"> 357<sect2 id="conf-files-patching">
358<title>Patching installation</title> 358<title>Patching installation</title>
359 359
360<para>As discussed above, <emphasis role="strong">packages themselves must not 360<para>As discussed above, <emphasis role="strong">packages themselves must not
361touch the contents of <filename>${PKG_SYSCONFDIR}</filename> 361touch the contents of <filename>${PKG_SYSCONFDIR}</filename>
362directly</emphasis>. Bad news is that many software installation scripts 362directly</emphasis>. Bad news is that many software installation scripts
363will, out of the box, mess with the contents of that directory. So what is 363will, out of the box, mess with the contents of that directory. So what is