[automake-commit] branch master updated: more HACKING tweaks

[Karl Berry]

This is an automated email from the git hooks/post-receive script.

karl pushed a commit to branch master
in repository automake.

View the commit online:
https://git.savannah.gnu.org/gitweb/?p=automake.git;a=commitdiff;h=96fd38d7e66152073f7e6ebcd9f7d513730dccc5

The following commit(s) were added to refs/heads/master by this push:
     new 96fd38d7e more HACKING tweaks
96fd38d7e is described below

commit 96fd38d7e66152073f7e6ebcd9f7d513730dccc5
Author: Karl Berry <karl@freefriends.org>
AuthorDate: Sat Oct 1 09:19:57 2022 -0700

    more HACKING tweaks
---
 HACKING | 26 +++++++++++---------------
 1 file changed, 11 insertions(+), 15 deletions(-)

diff --git a/HACKING b/HACKING
index 5f0effff3..248fd4b03 100644
--- a/HACKING
+++ b/HACKING
@@ -37,9 +37,9 @@
   $(FETCHFILES) variable in Makefile.am.  They should never be edited
   here.  All but one of them can be updated from respective upstreams
   with "make fetch" (this should be done especially before releases).
-  The only exception is 'lib/COPYING' (from FSF), which should be
-  updated by hand whenever the GPL gets updated (which shouldn't happen
-  that often anyway :-)
+  The only exceptions are help2man (install the current version) and
+  'lib/COPYING' (from FSF), which should be updated by hand whenever the
+  GPL gets updated (which shouldn't happen that often anyway :-).
 
 * All changes that are not trivial bug fixes must be mentioned in NEWS.
 
@@ -351,7 +351,7 @@
   runs the fastest on your machine.  We'll use -j12 in this document.
 
 * To summarize, here is a typical make check invocation:
-    make -j12 VERBOSE=1 keep_testdirs=yes check
+    make -j12 VERBOSE=1 check keep_testdirs=yes
 
 * Then check t/test-suite.log for the overall results.  The directory
   t/TESTNAME.dir is where the work will be left, if the test fails.
@@ -457,14 +457,14 @@
   The repository will always have its own "odd" number so we can easily
   distinguish net and repo versions.)
 
-* Run these commands, in this order:
-
+* Run these commands, in this order (as mentioned, adjust -j as desired):
     make bootstrap
-    make check keep_testdirs=yes
+    make -j12 check keep_testdirs=yes
     make maintainer-check
-    make distcheck
-    make check-no-trailing-backslash-in-recipes
-    make check-cc-no-c-o
+    make -j12 distcheck                                # regular distcheck
+    make -j12 distcheck AM_TESTSUITE_MAKE="make -j$j"  # parallelize makes
+    make -j12 check-no-trailing-backslash-in-recipes
+    make -j12 check-cc-no-c-o
 
   It is also advised to run "git clean -fdx" before invoking the
   bootstrap, to ensure a really clean rebuild.  However, it must
@@ -488,20 +488,17 @@
 * For stable releases you'll have to update the manuals at www.gnu.org.
 
   - Generate manuals (with the help of the standard gendocs.sh script):
-
        make web-manual
 
     The ready-to-be-uploaded manuals (in several formats) will be left
     in the 'doc/web-manuals' directory.
 
   - Commit the updated manuals to web CVS:
-
       make web-manual-update
 
     If your local username is different from your username at Savannah,
     you'll have to override the 'CVS_USER' make variable accordingly;
     for example:
-
       make web-manual-update CVS_USER=slattarini
 
   - Check for link errors, fix them, recheck until convergence:
@@ -529,8 +526,7 @@
   the version you sent to the automake list, as get archived on
   <https://lists.gnu.org/archive/html/automake/>).
 
------
-
+---------
 Copyright (C) 2003-2022 Free Software Foundation, Inc.
 
 This program is free software; you can redistribute it and/or modify