This is the mail archive of the
mailing list for the GCC project.
Re: Steering committee, please, consider using lzip instead of xz
- From: Antonio Diaz Diaz <antonio at gnu dot org>
- To: gcc at gcc dot gnu dot org
- Cc: "Matias A. Fonzo" <selk at dragora dot org>, Antonio Diaz Diaz <antonio at gnu dot org>
- Date: Thu, 08 Jun 2017 21:29:25 +0200
- Subject: Re: Steering committee, please, consider using lzip instead of xz
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <20170608094248.GU2154@tucnak>
Jakub Jelinek wrote:
You keep referencing the marketing pages of one of the formats comparing to
other formats, that can be hardly considered unbiased. Most of the
compression formats have similar kind of pages, usually biased as well.
The above article is intended to be a serious (and as unbiased as
possible) analysis of the xz format. AFAIK, this is the only analysis of
the xz format ever written. I can't find anything similar in the xz
site, the bzip2 site, nor in any of the two gzip sites. All
the formats document their file format and usually offer some kind of
benchmark, but that is all. If you know of any such analysis, specially
of xz or lzip, please share it.
BTW, writing such an in-dept analysis is a lot of work, and it hurts
when someone describes it as "marketing" without verifying it first. If
anybody finds any error or inaccuracy in the above article I'll be happy
to correct it. Thanks.
The choice of xz is that it is used very widely these days, which is
not the case of lzip.
IMHO It is pretty obvious that whatever format is chosen to distribute
the code of a major project (GCC, coreutils, linux) will become widely
used, and in the meanwhile the users without support for the new format
can fall back to the .gz tarball, which is not so much larger than the
current bzip2 tarball.