From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Ralf Corsepius <ralf.corsepius@rtems.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
jan.kratochvil@redhat.com, gdb@sourceware.org
Subject: Re: xz for the new release tip
Date: Thu, 01 Oct 2009 06:32:00 -0000 [thread overview]
Message-ID: <4AC44CE7.2050109@rtems.org> (raw)
In-Reply-To: <4AC44BC0.3070701@rtems.org>
On 10/01/2009 08:27 AM, Ralf Corsepius wrote:
> On 10/01/2009 08:19 AM, Mark Kettenis wrote:
>>> Date: Wed, 30 Sep 2009 22:28:57 +0200
>>> From: Jan Kratochvil<jan.kratochvil@redhat.com>
>>>
>>> Hi,
>>>
>>> while currently the sources are release both as .tar.gz and as
>>> .tar.bz2 would
>>> not it be worth to start using .xz as a replacement for the .bz2
>>> variant?
>>>
>>> 13406892 bytes: gdb-6.8.91.20090930.tar.xz (xz -9)
>>> xz -dc: real 0m1.226s user 0m1.190s sys 0m0.037s
>>>
>>> 18453837 bytes: gdb-6.8.91.20090930.tar.bz2
>>> bzip2 -dc: real 0m3.775s user 0m3.755s sys 0m0.019s
>>
>> Never heard of it, so my guess it isn't used widely enough yet to make
>> sense.
>
> Well, zz is the successor of lzma.
>
> It's supported as "dist compression" by modern autoconf's
> (autoconf-2.64)
Correction: automake (automake-1.11)
, it's the internal compression being used in rpm on
> modern Linux distros (Fedora, openSUSE), etc.
>
> Whether it's stable enough and has a longer term perspective is a
> different question or will prove to be a yet another temporary anecdote
> in compression tools is hard to tell - doubts are justified, IMHO.
>
> Ralf
>
>
>
next prev parent reply other threads:[~2009-10-01 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 20:30 Jan Kratochvil
2009-09-30 20:39 ` Daniel Jacobowitz
2009-10-01 6:19 ` Mark Kettenis
2009-10-01 6:27 ` Ralf Corsepius
2009-10-01 6:32 ` Ralf Corsepius [this message]
2009-10-01 6:38 ` Jan Kratochvil
2009-10-01 6:48 ` Ralf Corsepius
2009-10-01 6:55 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AC44CE7.2050109@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox