Fix README-* files

README-alpha is for alpha releases, which are not from Git or CVS, so
omit mention of that.  I'm not sure we'll ever do alpha releases, but
if we do, README-alpha assumes the tarballs are already bit.

Update README-hacking with info that was mistakenly put into
README-alpha.  Also mention Bison, needed for parse-date.y.

diff --git a/README-alpha b/README-alpha
index baf982a7b7c6b9fadcd86f770b9e394dbe1efe2e..e6d9071987f74148f8f21e41b29277f839c2cb78 100644 (file)
--- a/README-alpha
+++ b/README-alpha
@@ -3,40 +3,6 @@ This is GNU tar.
 This is a *pre-release* version, and not ready for production use yet.
 Please send comments and problem reports to <bug-tar@gnu.org>.
 
-If you have taken the sources from CVS you will need the following
-packages (or later) to build GNU tar.  We don't make any extra effort
-to accommodate older versions of these packages, so please make sure
-that you have the latest stable version.
-
-- Automake <http://www.gnu.org/software/automake/>
-- Autoconf <http://www.gnu.org/software/autoconf/>
-- Bison <http://www.gnu.org/software/bison/>
-- Gettext <http://www.gnu.org/software/gettext/>
-- Gzip <http://www.gnu.org/software/gzip/>
-- M4 <http://www.gnu.org/software/m4/>
-- Texinfo <http://www.gnu.org/software/texinfo>
-- Wget <http://www.gnu.org/software/wget/>
-
-As of this writing, the latest stable version of Gzip is 1.2.4 but we
-suggest using test version 1.3.5 (or later, if one becomes available).
-
-Valgrind <http://valgrind.org/> is also highly recommended, if
-Valgrind supports your architecture.
-
-Before building the package, run "bootstrap".  It will obtain gnulib
-and paxutils files from their Git repositories on Savannah.  Then, it will
-fetch the po files from tar page at Translation Project, and, finally, it
-will start autoconfiguration process.  Simply running bootstrap without
-arguments should do in most cases.
-
-Bootstrap reads its configuration from file bootstrap.conf located on the
-top of tar source tree.  Several options are provided that modify its
-behavior.  Run 'bootstrap --help' for a list.
-
-To only fetch auxiliary files from the network, run ./autopull.sh.
-To only generate files such as 'configure', without accessing the
-network, run ./autogen.sh.  The 'bootstrap' script does both.
-
 \f
 
 Copyright 2001-2022 Free Software Foundation, Inc.

diff --git a/README-hacking b/README-hacking
index 4c484a425d996d8af745087c6965f2c512ecf2d5..538eef2238e3aaaf6e9a7fcbdbc26e2af9580c5e 100644 (file)
--- a/README-hacking
+++ b/README-hacking
@@ -8,16 +8,23 @@ tar.  We do not make any efforts to accommodate older versions of
 these packages, so please make sure that you have the latest stable
 version.
 
-- Automake <http://www.gnu.org/software/automake/>
 - Autoconf <http://www.gnu.org/software/autoconf/>
+- Automake <http://www.gnu.org/software/automake/>
+- Bison <http://www.gnu.org/software/bison/>
 - M4 <http://www.gnu.org/software/m4/>
-- Texinfo <http://www.gnu.org/software/texinfo>
+- Gettext <http://www.gnu.org/software/gettext/>
 - Git <http://git.or.cz>
+- Gzip <http://www.gnu.org/software/gzip/>
+- Texinfo <http://www.gnu.org/software/texinfo>
+- Wget <http://www.gnu.org/software/wget/>
 
 Up-to-date compilers and libraries are also recommended, for better
 static checking.  You may be able to use an older compiler by building
 with 'make WERROR_CFLAGS='; if so, don't worry about its false alarms.
 
+Valgrind <http://valgrind.org/> is also highly recommended, if
+Valgrind supports your architecture.
+
 * Bootstrapping
 
 Obviously, if you are reading these notes, you did manage to clone
@@ -38,7 +45,17 @@ INSTALLATION).
 Normally you will have to run bootstrap only once. However, if you
 intend to hack on GNU tar, you might need to run it again later.
 There are lots of options that you may find useful in this case.
-See 'bootstrap --help' for a detailed list.
+See './bootstrap --help' for a detailed list.
+
+Bootstrapping obtains Gnulib and Paxutils files from their Git
+repositories on Savannah.  Then, it fetches translations from the
+Translation Project, and, finally, it builds files useful for
+configuration.  Simply running ./bootstrap without arguments should do
+in most cases.
+
+The file bootstrap.conf contains bootstrapping configuration.
+Several options are provided that modify its behavior.
+Run './bootstrap --help' for a list.
 
 To only fetch auxiliary files from the network, run ./autopull.sh.
 To only generate files such as 'configure', without accessing the