From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29936 invoked by alias); 27 Jan 2012 09:12:52 -0000 Received: (qmail 29921 invoked by uid 22791); 27 Jan 2012 09:12:51 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SARE_SUB_OBFU_Z,SPF_SOFTFAIL,TW_XZ X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 Jan 2012 09:12:37 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LYG0020094ANW00@a-mtaout20.012.net.il> for gdb@sourceware.org; Fri, 27 Jan 2012 11:12:36 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.228.102.195]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LYG002819KZ2680@a-mtaout20.012.net.il>; Fri, 27 Jan 2012 11:12:35 +0200 (IST) Date: Fri, 27 Jan 2012 09:12:00 -0000 From: Eli Zaretskii Subject: Re: xz-compressed release tarballs? In-reply-to: <201201262049.33716.vapier@gentoo.org> To: Mike Frysinger Cc: gdb@sourceware.org, jan.kratochvil@redhat.com, jim@meyering.net Reply-to: Eli Zaretskii Message-id: <83mx99zf1z.fsf@gnu.org> References: <87mx9a1ag4.fsf@rho.meyering.net> <20120126203148.GA30390@host2.jankratochvil.net> <83vcnyyww0.fsf@gnu.org> <201201262049.33716.vapier@gentoo.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00088.txt.bz2 > From: Mike Frysinger > Date: Thu, 26 Jan 2012 20:49:32 -0500 > Cc: Jan Kratochvil , > jim@meyering.net > > 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, 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.