From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jim@meyering.net, gdb@sourceware.org
Subject: Re: xz-compressed release tarballs?
Date: Thu, 26 Jan 2012 22:15:00 -0000 [thread overview]
Message-ID: <20120126213612.GA4184@host2.jankratochvil.net> (raw)
In-Reply-To: <83vcnyyww0.fsf@gnu.org>
On Thu, 26 Jan 2012 22:30:39 +0100, Eli Zaretskii wrote:
> > That slow bzip2 decompression is a continuous pain during packaging, staring
> > at bzip2 -dc on each gdb.spec debugging cycle.
>
> As long as we don't drop bz2 and gz, that pain will never go away.
gdb.src.rpm will just use gdb-7.4.tar.xz so the pain will be gone.
> 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.
Current state: Shipped .tar.gz and .tar.bz2.
Possibility (a): Ship .tar.gz, .tar.bz2 and .tar.xz.
Possibility (b) - preferred by me: Ship only .tar.gz and .tar.xz.
IMO there are only few systems which already handle .tar.bz2 and which still
do not handle .tar.xz. And those few system can use .tar.gz instead of
.tar.bz2.
Thanks,
Jan
next prev parent reply other threads:[~2012-01-26 22:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 20:22 Jim Meyering
2012-01-26 20:32 ` Jan Kratochvil
2012-01-26 21:31 ` Eli Zaretskii
2012-01-26 22:15 ` Jan Kratochvil [this message]
2012-01-26 23:10 ` Samuel Bronson
2012-01-27 1:49 ` Mike Frysinger
2012-01-27 9:13 ` Eli Zaretskii
2012-01-27 5:02 ` Joel Brobecker
2012-01-27 9:36 ` Eli Zaretskii
2012-01-30 19:08 ` Tom Tromey
2012-01-27 1:48 ` Mike Frysinger
2012-01-27 9:12 ` Eli Zaretskii
2012-01-27 18:41 ` Mike Frysinger
2012-01-28 8:21 ` Eli Zaretskii
2012-01-28 23:08 ` Mike Frysinger
2012-01-29 3:55 ` Eli Zaretskii
2012-01-30 6:26 ` Mike Frysinger
2012-01-30 17:49 ` Alfred M. Szmidt
2012-01-30 19:54 ` Stan Shebs
2012-01-30 20:53 ` Pedro Alves
2012-01-30 21:06 ` Mike Frysinger
2012-01-27 2:37 ` Ralf Corsepius
2012-01-27 9:26 ` Jan Kratochvil
2012-01-27 20:27 ` Mike Frysinger
2012-01-27 20:30 ` Marek Polacek
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=20120126213612.GA4184@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jim@meyering.net \
/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