From: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: xz-compressed release tarballs?
Date: Mon, 30 Jan 2012 20:53:00 -0000 [thread overview]
Message-ID: <4F270353.8010609@redhat.com> (raw)
In-Reply-To: <4F26F55C.8050408@earthlink.net>
On 01/30/2012 07:54 PM, 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.
Indeed.
Keeping things in perspective, it doesn't seem like we're at the verge of a shift of
mentality where people are rushing out to wack out all legacy support from GDB. Although, it has
been pointed out that several GNU packages are already shipping xz only, including coreutils and
grep, without complaint -- this is a very good indication that dropping .gz isn't that much of
an obstacle as one might think at first sight. But, for GDB, let's leave that for some other
day in the somewhat distant future, and move on.
The options on the table were:
(a) tar.gz, tar.bz2, tar.xz
(b) tar.gz, tar.xz
(c) tar.gz, tar.bz2 (status quo, do nothing, for completeness)
tar.gz was still there in all proposals, which caters to older, legacy systems.
I'm also in favor of replacing .bz2 with .xz, keeping .gz, option (b), and it
seemed to me it got the popular vote. IMO, Just Do It (TM).
--
Pedro Alves
next prev parent reply other threads:[~2012-01-30 20:53 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
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 [this message]
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=4F270353.8010609@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).