How about stopping new *.tar.bz2 releases?
Current ruby releases generate
But I think we can stop generating
*.tar.bz2 are less merit.
For better size,
For better compatibility,
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 use
*.tar.bz2. And it can use
Updated by shevegen (Robert A. Heiler) about 2 months ago
I don't mind as in I don't need .tar.bz2.
Personally I use .tar.xz; all local archives of source files that I
keep are in .tar.xz format.
(Note that github offers either git clone, or .zip, so .tar.bz2 is
probably becoming more rare every year.)
Updated by Eregon (Benoit Daloze) about 2 months ago
ruby-install also uses
.tar.bz2 currently, so changing that would mean that existing ruby-install releases (and installations) would no longer work:
Not sure about RVM.
Updated by shan (Shannon Skipper) about 2 months ago
If bz2 removal goes forward, it might be nice to deprecate now but not remove until later. It'd be ideal to have working versions of RVM, ruby-install and ruby-build in wide distribution before bz2 goes away. If we change the tools now but don't remove bz2 for a few years, I think it'd go smoother without having users tempted to bypass checksums.
For ruby-install, users will have to upgrade the tool itself to move off bz2. It uses a different repo, ruby-versions, for checksums, so it already has xz, etc. But, the choice of bz2 is hardcoded in ruby-install. Currently, bz2 is used for Ruby and Rubinius and tar is used for MRuby, JRuby and TruffleRuby. Only small code changes are necessary, but everyone would have to upgrade the tool rather than just using the --latest flag to fetch the latest Ruby metadata like normal. Since metadata isn't handled in the tool itself, ruby-install isn't updated frequently. Users tend not to upgrade often and it doesn't have a self-update mechanism.
RVM has bz2 md5 and sha512 checksums hardcoded inline, so it's just the RVM repo to update to new checksums. RVM already has tooling to support alternative decompression, but I'm not sure where all else bz2 might be intertwined. It's probably not too bad after changing a bunch of checksums. Users would need to get an updated version of RVM for bz2 support too, but that's also the normal upgrade mechanism for access to new Ruby metadata—so it's normal for RVM users to upgrade fairly often.