Re: binutils-2.13.tar.bz2

[Andrew Cagney <ac131313 at ges dot redhat dot com>]

> On Thu, Aug 08, 2002 at 12:05:03PM -0400, Graeme Peterson wrote:
>
> > Hi, all.
> >
> > I may have missed the e-mails discussing this, but is
> > there a reason why the binutils-2.13 tarball and upgrade
> > patch are only posted in bz2 format?  I found, built and 
> > used bzip2, but it seems inconvenient to expect the world
> > to have to do that.
> >
> >   $ ftp ftp://ftp.gnu.org
> >   Connected to ftp.gnu.org.
> >   
> >         <snip big blurb>
> >   
> >   ftp> cd gnu/binutils
> >   250 Directory successfully changed.
> >   ftp> pwd
> >   257 "/gnu/binutils"
> >   ftp> ls *2.13*
> >   200 PORT command successful. Consider using PASV.
> >   150 Here comes the directory listing.
> >   -rw-r--r--    1 0        0         2177752 Aug 06 14:40 binutils-2.12.1-2.13-patch.bz2
> >   -rw-r--r--    1 0        0         9882367 Aug 06 14:40 binutils-2.13.tar.bz2
> >   226 Directory send OK.
> >   ftp>
> >
> > Thanks.
>
> Because the makefile currently makes bz2 tarballs? :)  I'll put up
> gzipped versions in a little bit, thanks for the reminder.
Have a look at what GDB does here.

I changed the release process, and top level Makefile.in, so that it can 
create a simple .tar file.  The .bz2 and .gz are then created by hand 
(but note that it doesn't use `gzip < .tar > .tar.gz2`).

Not having to do `bunzip2 ; gzip` carved a suprising amount of time off 
the release process!

enjoy,
Andrew

http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC150
See ``Create compressed versions of the release''.