Re: [rfa] doc/gdbint.texinfo: update commands for release tarball

Re: [rfa] doc/gdbint.texinfo: update commands for release tarball

[Michael Elizabeth Chastain]

Andrew C writes:
> The section `Configuring @value{GDBN} for Release' should be deleted. 
> It's been entirely superseeded by the chapter `Releasing GDB'.

Ah, okay, I will delete that section and edit this part:

  @smallexample
  $  for m in gdb insight
  do
  ( cd $m/src && gmake -f Makefile.in $m.tar )
  done
  $  ( m=dejagnu; cd $m/src && gmake -f Makefile.in $m.tar.bz2 )
  @end smallexample

Michael C

Re: [rfa] doc/gdbint.texinfo: update commands for release tarball

[Andrew Cagney]

> Andrew C writes:
> 
>> The section `Configuring @value{GDBN} for Release' should be deleted. 
>> It's been entirely superseeded by the chapter `Releasing GDB'.
> 
> 
> Ah, okay, I will delete that section and edit this part:
> 
>   @smallexample
>   $  for m in gdb insight
>   do
>   ( cd $m/src && gmake -f Makefile.in $m.tar )
>   done
>   $  ( m=dejagnu; cd $m/src && gmake -f Makefile.in $m.tar.bz2 )
>   @end smallexample

For the moment, I think clone it.  (but add a cindex?)

I cut/paste these sequeces when doing a release (which is why they keep 
changing) so having just the new one there would break me doing a 
re-spin of the current branch :-)

Andrew

Re: [rfa] doc/gdbint.texinfo: update commands for release tarball

[Michael Elizabeth Chastain]

> I cut/paste these sequeces when doing a release (which is why they keep 
> changing) so having just the new one there would break me doing a 
> re-spin of the current branch :-)

Mmm, shouldn't you cut/paste out of doc/gdbint.texinfo in the
branch when you are spinning the branch?

> For the moment, I think clone it.  (but add a cindex?)

I'm willing to clone it if I can't convince you to look in the right
place.  :)

It just really frustrated me yesterday when you said 'there's a problem
in the snapshot tarball' and I could not make a snapshot tarball.
That's why I am keen on this.

Michael C

Re: [rfa] doc/gdbint.texinfo: update commands for release tarball

[Andrew Cagney]

> This patch updates gdbint.texinfo with the new instructions for making
> a release tarball.
> 
> 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 a fresh tree and I got some nice
> looking tarballs.
> 
> OK to apply?

The section `Configuring @value{GDBN} for Release' should be deleted. 
It's been entirely superseeded by the chapter `Releasing GDB'.

enjoy,
Andrew


> Michael C
> 
> 2003-01-09  Michael Chastain  <mec@shout.net>
> 
> 	* gdb.texinfo (Configuring @value{GDBN} for Release): Update
> 	to "make -f src-release gdb.tar".
> 
> 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	9 Jan 2003 22:16:03 -0000
> @@ -5404,14 +5404,16 @@
>  @file{libiberty}, and so on):
>  
>  @smallexample
> -make -f Makefile.in gdb.tar.gz
> +make -f src-release gdb.tar
> +version=2003-01-09-cvs
> +bzip2 -v -9 -c gdb-$version.tar > gdb-$version.tar.bz2
> +gzip -v -9 -c gdb-$version*.tar > gdb-$version.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.)
> +and will then make a tarfile.
>  
>  This procedure requires:
>  
> 

[rfa] doc/gdbint.texinfo: update commands for release tarball

[Michael Elizabeth Chastain]

This patch updates gdbint.texinfo with the new instructions for making
a release tarball.

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 a fresh tree and I got some nice
looking tarballs.

OK to apply?

Michael C

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

	* gdb.texinfo (Configuring @value{GDBN} for Release): Update
	to "make -f src-release gdb.tar".

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	9 Jan 2003 22:16:03 -0000
@@ -5404,14 +5404,16 @@
 @file{libiberty}, and so on):
 
 @smallexample
-make -f Makefile.in gdb.tar.gz
+make -f src-release gdb.tar
+version=2003-01-09-cvs
+bzip2 -v -9 -c gdb-$version.tar > gdb-$version.tar.bz2
+gzip -v -9 -c gdb-$version*.tar > gdb-$version.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.)
+and will then make a tarfile.
 
 This procedure requires: