xz-compressed release tarballs?

Eli Zaretskii eliz@gnu.org
Sat Jan 28 08:21:00 GMT 2012


> From: Mike Frysinger <vapier@gentoo.org>
> Date: Fri, 27 Jan 2012 13:41:40 -0500
> Cc: gdb@sourceware.org,
>  jan.kratochvil@redhat.com,
>  jim@meyering.net
> 
> On Friday 27 January 2012 04:10:32 Eli Zaretskii wrote:
> > From: Mike Frysinger <vapier@gentoo.org>
> > > On Thursday 26 January 2012 16:30:39 Eli Zaretskii wrote:
> > > > > Previous proposal by me:
> > > > > 	xz for the new release tip
> > > > > 	http://sourceware.org/ml/gdb/2009-09/msg00341.html
> > > > 
> > > > Please think a little about those who don't necessarily have a tar
> > > > that knows about xz.  The world doesn't end with GNU/Linux.
> > > 
> > > why does tar have to know about xz ?  stdin hasn't suddenly stopped
> > > working.
> > > 
> > > 	xzcat foo.tar.xz | tar xf -
> > 
> > Because (a) this is less convenient to type
> 
> you gotta be pulling my leg with this

No more than you are pulling mine with a few extra bytes.

> > and (b) you assume that ports of tar to non-Posix platforms know how to read
> > binary streams from stdin, but that assumption is false in quite a few
> > existing and widely used ports of tar.
> 
> still a non-issue:
> 	unxz foo.tar.xz
> 	tar xf foo.tar

So is pulling a few extra bytes through the wire.

> forcing people to live in the past because you can't be bothered to type a few 
> extra characters on your legacy systems is ridiculous

I see nothing ridiculous in a request to cater to a situation of your
fellow developer of Free Software, and don't understand how can you
ridicule such a request.



More information about the Gdb mailing list