From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29412 invoked by alias); 30 Jan 2012 21:06:54 -0000 Received: (qmail 29403 invoked by uid 22791); 30 Jan 2012 21:06:53 -0000 X-SWARE-Spam-Status: No, hits=-4.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SARE_SUB_OBFU_Z,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 30 Jan 2012 21:06:40 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 2A59C1B4008; Mon, 30 Jan 2012 21:06:40 +0000 (UTC) From: Mike Frysinger To: gdb@sourceware.org Subject: Re: xz-compressed release tarballs? Date: Mon, 30 Jan 2012 21:06:00 -0000 User-Agent: KMail/1.13.7 (Linux/3.2.0; KDE/4.6.5; x86_64; ; ) Cc: Stan Shebs References: <87mx9a1ag4.fsf@rho.meyering.net> <201201281809.17343.vapier@gentoo.org> <4F26F55C.8050408@earthlink.net> In-Reply-To: <4F26F55C.8050408@earthlink.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart17736644.kcAIfPLxeK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201201301606.41259.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/msg00122.txt.bz2 --nextPart17736644.kcAIfPLxeK Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-length: 831 On Monday 30 January 2012 14:54:04 Stan Shebs wrote: > So while we can certainly debate whether this feature or that helps or > hinders future progress, I don't think it's in our interests to > disparage all the legacy support. i didn't say "legacy isn't supported at all". xz will work on legacy syste= ms=20 just fine provided you d/l and build the decompressor (which is freely=20 available). what i did say is that we can't restrict ourselves based on wh= at=20 random old versions of tar people have on their random systems which happen= s=20 to not detect xz transparently. your `tar` doesn't support -J, or -I, or -a doesn't detect xz ? then run=20 `unxz` yourself first. there is no actual problem here. the only thing i'= ve=20 seen from Eli is that he doesn't want to have to run `unxz ... && tar xf ..= .`. -mike --nextPart17736644.kcAIfPLxeK Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 836 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJPJwZhAAoJEEFjO5/oN/WBbQ4P/2fzFd8wh3GDn//sSzM5q5Ms uSvOMuGxFRTWkvjI/y+0az5MH+Teh+bu33Hj+W6r0vZPwZE7brOI3Iwt4H05Qn9g cbsXOf1KNOvV3eXdHaijnkdjctrIKKvT7Fj1H9Ao5NRZ1hnngzdG8Z4mcPEP8bcd 7k4IhdNiI/S0mL3v94/4RqKJXh7Z4eCmE81Lygwl5TmLk1liuETFDiIlxbOmWWT0 Rst6h1YV4iyOFStiWGpZLr2ufdX/+GXXgym575hT+8BcwowduhWjCdr2NoYxLdum DCKgPEnpxRqSsAtRL0ALceK2L5jLZs+A5cniG+FKgxE5LRueWtGQuQPqpFG0yhSs KxR93sh6iXFy8KkzDycTmJWMyd+2VtIDOrqrTTVuky6dSLWfM0yoB8Y+NuH+OJxB RrbheF4v6OPkcqL/+yle7u0adzg4VUZ2WG3/vraGqlreL5zx4YGDRfL8dhUChd91 sGDkJp17R32WFm5R90fWyu+2+REaZIHqbpqu6LAITPie8/rQeQmCpu29jdYLudTZ rWL29CwcG5LSmHa2l48AmaVWCTJKDpbuKuXOmyZM+Ty9572OWzW0+LUoZ97mLcQx ANUjkth4dRLbFi76oQ+V5tJHdMVS7cnaTLFv4QR12YAhssbhoULXy/XZYd+sfQOt eLAySaatTYP3y0h1B9BJ =kpA1 -----END PGP SIGNATURE----- --nextPart17736644.kcAIfPLxeK--