From: Karl Berry <karl@freefriends.org>
Date: Wed, 25 Jun 2025 20:52:29 +0000 (-0700)
Subject: doc: key maintenance, wording.
X-Git-Tag: v1.18.1~2
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1f4ff701965df6bffc4dc116a398622be5a3a93e;p=thirdparty%2Fautomake.git

doc: key maintenance, wording.

* HACKING: mention a couple of links wrt key maintenance.
* doc/automake.texi: wording tweaks.
---

diff --git a/HACKING b/HACKING
index f060e0ded..3d3532477 100644
--- a/HACKING
+++ b/HACKING
@@ -673,6 +673,17 @@
   to do this for all kinds of releases, again to help pretests be seen
   and actually tested by as many people as possible.
 
+* Key maintenance: new maintainers uploading releases need to follow the
+  instructions in
+  https://gnu.org/prep/maintain/maintain.html#Automated-Upload-Registration.
+  The FSF sysadmins may need to be reminded to install new keys.
+  
+  A preliminary step is to check
+  https://savannah.gnu.org/project/release-gpgkeys.php?group=automake
+  which has a link to download automake-keyring.gpg; the new key should
+  be installed there. You can list the keys present with
+  gpg --show-keys automake-keyring.gpg # N.B. not --list-keys
+
 ---------
 Copyright (C) 2003-2025 Free Software Foundation, Inc.
 
diff --git a/doc/automake.texi b/doc/automake.texi
index 2f7d4a3b7..76656babe 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -678,7 +678,7 @@ Furthermore it may help to diagnose an incomplete installation.
 
 Presently most packages do not have any @code{installcheck} tests
 because the existence of @code{installcheck} is little known, and its
-usefulness is neglected.  Our little toy package is no better: @code{make
+usefulness is neglected.  Our toy package is no better: @code{make
 installcheck} does nothing.
 
 @node Standard Targets
@@ -691,37 +691,40 @@ Build System: @code{make}, @code{make check}, @code{make install}, and
 @dfn{targets}.  @code{make} is a shorthand for @code{make all},
 @code{all} being the default target in the GNU Build System.
 
-Here is a list of the most useful targets that the GNU Coding Standards
-specify.
+Here is a list of the most commonly useful targets that the GNU Coding
+Standards specify.
 
 @table @code
 @item make all
 @trindex all
 Build programs, libraries, documentation, etc.@: (same as @code{make}).
+
 @item make install
 @trindex install
 Install what needs to be installed, copying the files from the
 package's tree to system-wide directories.
-@item make install-strip
-@trindex install-strip
-Same as @code{make install}, then strip debugging symbols.  Some
-users like to trade space for useful bug reports@enddots{}
+
 @item make uninstall
 @trindex uninstall
 The opposite of @code{make install}: erase the installed files.
 (This needs to be run from the same build tree that was installed.)
+
 @item make clean
 @trindex clean
 Erase from the build tree the files built by @code{make all}.
+
 @item make distclean
 @trindex distclean
 Additionally erase anything @code{./configure} created.
+
 @item make check
 @trindex check
 Run the test suite, if any.
+
 @item make installcheck
 @trindex installcheck
 Check the installed programs or libraries, if supported.
+
 @item make dist
 @trindex dist
 Recreate @file{@var{package}-@var{version}.tar.gz} from all the source