From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mec@shout.net>
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Received: (qmail 9578 invoked from network); 10 Jan 2003 20:34:50 -0000
Received: from unknown (HELO duracef.shout.net) (204.253.184.12)
  by 209.249.29.67 with SMTP; 10 Jan 2003 20:34:50 -0000
Received: (from mec@localhost)
	by duracef.shout.net (8.11.6/8.11.6) id h0AKYcW27845
	for gdb-patches@sources.redhat.com; Fri, 10 Jan 2003 14:34:38 -0600
Date: Fri, 10 Jan 2003 20:34:00 -0000
From: Michael Elizabeth Chastain <mec@shout.net>
Message-Id: <200301102034.h0AKYcW27845@duracef.shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa] gdb.texinfo: new release tarball commands
X-SW-Source: 2003-01/txt/msg00411.txt.bz2

This patch updates gdbint.texinfo with the new instructions for making
a release tarball.  This is version #2 of this patch.

This time, I removed the whole section "Configuring @value{GDBN} for
Release".  Also, I added instructions for older versions of gdb which
do not have @file{src-release} (gdb 5.3.1 and older).

Note that more people than the release manager need this information.
I wrote this patch because I needed to know how snapshot tarballs were
made in order to debug a problem with testsuite/gdb.c++ files inside
the current snapshots.

Testing: I followed the instructions on gdb HEAD, gdb gdb_5_3-branch,
insight HEAD, insight gdb_5_3-banch, and dejagnu HEAD.  They worked.

OK to apply?

Michael C

2003-01-09  Michael Chastain  <mec@shout.net>

	* gdbint.texinfo (Configuring @value{GDBN} for Release): Delete.
	(Create a Release): Add new instructions for new @file{src-release}.
	Document existing instructions for @file{Makefile.in} as
	being for @value{GDBN} 5.3.1 or earlier.

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.115
diff -u -r1.115 gdbint.texinfo
--- gdbint.texinfo	9 Jan 2003 18:46:02 -0000	1.115
+++ gdbint.texinfo	10 Jan 2003 20:03:37 -0000
@@ -5396,62 +5396,6 @@
 configuration.
 @end itemize
 
-@section Configuring @value{GDBN} for Release
-
-@cindex preparing a release
-@cindex making a distribution tarball
-From the top level directory (containing @file{gdb}, @file{bfd},
-@file{libiberty}, and so on):
-
-@smallexample
-make -f Makefile.in gdb.tar.gz
-@end smallexample
-
-@noindent
-This will properly configure, clean, rebuild any files that are
-distributed pre-built (e.g. @file{c-exp.tab.c} or @file{refcard.ps}),
-and will then make a tarfile.  (If the top level directory has already
-been configured, you can just do @code{make gdb.tar.gz} instead.)
-
-This procedure requires:
-
-@itemize @bullet
-
-@item 
-symbolic links;
-
-@item
-@code{makeinfo} (texinfo2 level);
-
-@item
-@TeX{};
-
-@item
-@code{dvips};
-
-@item
-@code{yacc} or @code{bison}.
-@end itemize
-
-@noindent
-@dots{} and the usual slew of utilities (@code{sed}, @code{tar}, etc.).
-
-@subheading TEMPORARY RELEASE PROCEDURE FOR DOCUMENTATION
-
-@file{gdb.texinfo} is currently marked up using the texinfo-2 macros,
-which are not yet a default for anything (but we have to start using
-them sometime).
-
-For making paper, the only thing this implies is the right generation of
-@file{texinfo.tex} needs to be included in the distribution.
-
-For making info files, however, rather than duplicating the texinfo2
-distribution, generate @file{gdb-all.texinfo} locally, and include the
-files @file{gdb.info*} in the distribution.  Note the plural;
-@code{makeinfo} will split the document into one overall file and five
-or so included files.
-
-
 @node Releasing GDB
 
 @chapter Releasing @value{GDBN}
@@ -5983,6 +5927,17 @@
 @subsubheading Do the dirty work
 
 This is identical to the process used to create the daily snapshot.
+
+@smallexample
+$  for m in gdb insight
+do
+( cd $m/src && gmake -f src-release $m.tar )
+done
+$  ( m=dejagnu; cd $m/src && gmake -f src-release $m.tar.bz2 )
+@end smallexample
+
+If the top level source directory does not have @file{src-release}
+(@value{GDBN} version 5.3.1 or earlier), try these commands instead.
 
 @smallexample
 $  for m in gdb insight