From: shannonskipper@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:96700] [Ruby master Misc#16483] How about stopping new *.tar.bz2 releases?
Date: Tue, 07 Jan 2020 07:10:12 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-83685.20200107071011.de2a3b8848c14025@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16483.20200106070219@ruby-lang.org
Issue #16483 has been updated by shan (Shannon Skipper).
RVM also primarily uses bz2.
----------------------------------------
Misc #16483: How about stopping new *.tar.bz2 releases?
https://bugs.ruby-lang.org/issues/16483#change-83685
* Author: znz (Kazuhiro NISHIYAMA)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Current ruby releases generate `*.tar.gz`, `*.tar.bz2`, `*.tar.xz`, and `*.zip`.
But I think we can stop generating `*.tar.bz2`.
I think `*.tar.bz2` are less merit.
For better size, `*.tar.xz` exist.
For better compatibility, `*.tar.gz` and `*.zip` exist.
I check some programming languages source package archives.
- https://jdk.java.net/13/ tar.gz zip
- https://gcc.gnu.org/mirrors.html tar.gz tar.xz
- https://www.python.org/downloads/source/ tgz tar.xz
- https://nodejs.org/dist/v12.14.0/ tar.gz tar.xz (and 7z zip for win)
- https://www.perl.org/get.html tar.gz
- https://www.php.net/downloads.php tar.bz2 tar.gz tar.xz
`tar.bz2` are rare.
How about stopping `*.tar.bz2` since next release?
(I know [ruby-build](https://github.com/rbenv/ruby-build) use `*.tar.bz2`. And it can use `*.tar.gz`)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2020-01-07 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16483.20200106070219@ruby-lang.org>
2020-01-06 7:02 ` [ruby-core:96681] [Ruby master Misc#16483] How about stopping new *.tar.bz2 releases? zn
2020-01-06 7:59 ` [ruby-core:96684] " shevegen
2020-01-06 8:50 ` [ruby-core:96686] " XrXr
2020-01-06 18:15 ` [ruby-core:96692] " eregontp
2020-01-07 4:38 ` [ruby-core:96699] " hsbt
2020-01-07 7:10 ` shannonskipper [this message]
2020-01-08 0:38 ` [ruby-core:96707] " shannonskipper
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-83685.20200107071011.de2a3b8848c14025@ruby-lang.org \
--to=ruby-core@ruby-lang.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).