[pkgsrc/trunk]: pkgsrc/doc doc/pkgsrc.*: regen

[gutteridge <gutteridge%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/6af920cbcfc7
branches:  trunk
changeset: 377014:6af920cbcfc7
user:      gutteridge <gutteridge%pkgsrc.org@localhost>
date:      Fri Apr 15 13:51:23 2022 +0000

description:
doc/pkgsrc.*: regen

diffstat:

 doc/pkgsrc.html |  1525 +++++++++++++++++++++++++-----------------------------
 doc/pkgsrc.txt  |  1494 ++++++++++++++++++++++++++---------------------------
 2 files changed, 1439 insertions(+), 1580 deletions(-)

diffs (truncated from 3904 to 300 lines):

diff -r f7316960895c -r 6af920cbcfc7 doc/pkgsrc.html
--- a/doc/pkgsrc.html   Fri Apr 15 13:51:07 2022 +0000
+++ b/doc/pkgsrc.html   Fri Apr 15 13:51:23 2022 +0000
@@ -3663,8 +3663,8 @@
   problems.</p>
 <p>For even more automation, we recommend using
   <span class="command"><strong>mkpatches</strong></span> from the same package to make a
-  whole set of patches. You just have to backup files before you
-  edit them to <code class="filename">filename.orig</code>, e.g. with
+  whole set of patches. You just have to back up files before you
+  edit them to <code class="filename">filename.orig</code>, e.g., with
   <span class="command"><strong>cp -p filename filename.orig</strong></span> or, easier, by
   using <span class="command"><strong>pkgvi</strong></span> again from the same package. If
   you upgrade a package this way, you can easily compare the new
@@ -3688,6 +3688,13 @@
   but new patches should be of the form containing the filename.
   <span class="command"><strong>mkpatches</strong></span> included in <a href="https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/pkgtools/pkgdiff/index.html"; target="_top"><code 
class="filename">pkgtools/pkgdiff</code></a> takes care of the name
   automatically.</p>
+<p>When updating pre-existing patch files, if a file uses the old
+  <code class="filename">patch-<em class="replaceable"><code>[a-z][a-z]</code></em></code>
+  convention, it's best not to change it to the new form, as that will
+  just cause churn that makes it harder to track changes to patching
+  over time. Similarly, if a patch now applies at different line offsets,
+  but still applies cleanly as-is, there's no need to update it, as that
+  also unnecessarily complicates the patch history.</p>
 </div>
 <div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
@@ -11726,116 +11733,112 @@
 <td>ALL_ENV</td>
 </tr>
 <tr>
-<td>ALSA_PC</td>
 <td>ALTERNATIVES_SRC</td>
-</tr>
-<tr>
 <td>AMANDA_TMP</td>
+</tr>
+<tr>
 <td>AMANDA_USER</td>
-</tr>
-<tr>
 <td>AMANDA_VAR</td>
+</tr>
+<tr>
 <td>APACHE_GROUP</td>
-</tr>
-<tr>
 <td>APACHE_MODULE_NAME</td>
+</tr>
+<tr>
 <td>APACHE_MODULE_SRC</td>
-</tr>
-<tr>
 <td>APACHE_MODULE_SRCDIR</td>
+</tr>
+<tr>
 <td>APACHE_PKG_PREFIX</td>
-</tr>
-<tr>
 <td>APACHE_SUEXEC_CONFIGURE_ARGS</td>
+</tr>
+<tr>
 <td>APACHE_SUEXEC_DOCROOT</td>
-</tr>
-<tr>
 <td>APACHE_USER</td>
+</tr>
+<tr>
 <td>APPEND_ABI</td>
-</tr>
-<tr>
 <td>APPEND_ELF</td>
+</tr>
+<tr>
 <td>ARLA_CACHE</td>
-</tr>
-<tr>
 <td>AUDIT_PACKAGES_FLAGS</td>
+</tr>
+<tr>
 <td>AUTOCONF_REQD</td>
-</tr>
-<tr>
 <td>AUTOMAKE_OVERRIDE</td>
+</tr>
+<tr>
 <td>AUTOMAKE_REQD</td>
-</tr>
-<tr>
 <td>AUTO_MKDIRS</td>
+</tr>
+<tr>
 <td>BDB185_DEFAULT</td>
-</tr>
-<tr>
 <td>BDBBASE</td>
+</tr>
+<tr>
 <td>BDB_ACCEPTED</td>
-</tr>
-<tr>
 <td>BDB_DEFAULT</td>
+</tr>
+<tr>
 <td>BDB_LIBS</td>
-</tr>
-<tr>
 <td>BDB_TYPE</td>
+</tr>
+<tr>
 <td>BINCIMAP_GROUP</td>
-</tr>
-<tr>
 <td>BINCIMAP_USER</td>
+</tr>
+<tr>
 <td>BIND_DIR</td>
-</tr>
-<tr>
 <td>BIND_GROUP</td>
+</tr>
+<tr>
 <td>BIND_USER</td>
-</tr>
-<tr>
 <td>BINOWN</td>
+</tr>
+<tr>
 <td>BINPKG_SITES</td>
-</tr>
-<tr>
 <td>BIN_INSTALL_FLAGS</td>
+</tr>
+<tr>
 <td>BISON_PKGDATADIR</td>
-</tr>
-<tr>
 <td>BLAS</td>
+</tr>
+<tr>
 <td>BLAS_ACCEPTED</td>
-</tr>
-<tr>
 <td>BLAS_C_INTERFACE</td>
+</tr>
+<tr>
 <td>BLAS_INCLUDES</td>
-</tr>
-<tr>
 <td>BLAS_INDEX64</td>
+</tr>
+<tr>
 <td>BLAS_LIBS</td>
-</tr>
-<tr>
 <td>BLAS_TYPE</td>
+</tr>
+<tr>
 <td>BOOTSTRAP_DEPENDS</td>
-</tr>
-<tr>
 <td>BROKEN</td>
+</tr>
+<tr>
 <td>BROKEN_EXCEPT_ON_PLATFORM</td>
-</tr>
-<tr>
 <td>BROKEN_ON_PLATFORM</td>
+</tr>
+<tr>
 <td>BSDSRCDIR</td>
-</tr>
-<tr>
 <td>BSDXSRCDIR</td>
+</tr>
+<tr>
 <td>BSD_MAKE_ENV</td>
-</tr>
-<tr>
 <td>BUILDLINK_AUTO_DIRS</td>
+</tr>
+<tr>
 <td>BUILDLINK_AUTO_VARS</td>
-</tr>
-<tr>
 <td>BUILDLINK_CFLAGS</td>
+</tr>
+<tr>
 <td>BUILDLINK_CONTENTS_FILTER</td>
-</tr>
-<tr>
 <td>BUILDLINK_CPPFLAGS</td>
-<td>BUILDLINK_DEPMETHOD</td>
 </tr>
 <tr>
 <td>BUILDLINK_FILES</td>
@@ -11927,107 +11930,95 @@
 </tr>
 <tr>
 <td>CDROM_PKG_URL_HOST</td>
-<td>CHECKOUT_DATE</td>
-</tr>
-<tr>
 <td>CHECK_COMPILER</td>
+</tr>
+<tr>
 <td>CHECK_FAKEHOME</td>
-</tr>
-<tr>
 <td>CHECK_FILES</td>
+</tr>
+<tr>
 <td>CHECK_FILES_SKIP</td>
-</tr>
-<tr>
 <td>CHECK_FILES_STRICT</td>
+</tr>
+<tr>
 <td>CHECK_HEADERS</td>
-</tr>
-<tr>
 <td>CHECK_HEADERS_SKIP</td>
+</tr>
+<tr>
 <td>CHECK_INTERPRETER</td>
-</tr>
-<tr>
 <td>CHECK_INTERPRETER_SKIP</td>
+</tr>
+<tr>
 <td>CHECK_PERMS</td>
-</tr>
-<tr>
 <td>CHECK_PERMS_AUTOFIX</td>
+</tr>
+<tr>
 <td>CHECK_PERMS_SKIP</td>
-</tr>
-<tr>
 <td>CHECK_PIE</td>
+</tr>
+<tr>
 <td>CHECK_PIE_SKIP</td>
-</tr>
-<tr>
 <td>CHECK_PIE_SUPPORTED</td>
+</tr>
+<tr>
 <td>CHECK_PORTABILITY</td>
-</tr>
-<tr>
 <td>CHECK_PORTABILITY_EXPERIMENTAL</td>
+</tr>
+<tr>
 <td>CHECK_PORTABILITY_SKIP</td>
-</tr>
-<tr>
 <td>CHECK_RELRO</td>
+</tr>
+<tr>
 <td>CHECK_RELRO_SKIP</td>
-</tr>
-<tr>
 <td>CHECK_RELRO_SUPPORTED</td>
+</tr>
+<tr>
 <td>CHECK_SHLIBS</td>
-</tr>
-<tr>
 <td>CHECK_SHLIBS_SKIP</td>
+</tr>
+<tr>
 <td>CHECK_SHLIBS_SUPPORTED</td>
-</tr>
-<tr>
 <td>CHECK_SHLIBS_TOXIC</td>
+</tr>
+<tr>
 <td>CHECK_SSP</td>
-</tr>
-<tr>
 <td>CHECK_SSP_SKIP</td>
+</tr>
+<tr>
 <td>CHECK_SSP_SUPPORTED</td>
-</tr>
-<tr>
 <td>CHECK_STRIPPED</td>
+</tr>
+<tr>
 <td>CHECK_STRIPPED_SKIP</td>
-</tr>
-<tr>
 <td>CHECK_WRKREF</td>
+</tr>
+<tr>
 <td>CHECK_WRKREF_EXTRA_DIRS</td>
-</tr>
-<tr>