now that gcc-core and all other tarballs are merged into a single, huge 83 MB bzip2 tarball, i waste serious time whenever i rebuild my linux distro in qemu.
unpacking the official .bz2 tarball on qemu/mips takes nearly 2 hours (!)
since it is unlikely that i could convince you to go back to the former distribution strategy, i suggest shipping the tarballs additionally in .xz format, which is 3-4 times faster to extract.
i compared speeds of the official gcc 4.7.0 bzip2 tarballs vs a .xz version i made out of the former.
/dev/shm $ cp ~/Downloads/gcc-4.7.2.tar.bz2 .
/dev/shm $ time tar xf gcc-4.7.2.tar.bz2
/dev/shm $ tar cJf gcc-4.7.2.tar.xz gcc-4.7.2
/dev/shm $ la gcc-4.7.2.tar.xz
-rw-r--r-- 1 roger users 66696632 Oct 29 21:50 gcc-4.7.2.tar.xz
/dev/shm $ la gcc-4.7.2.tar.bz2
-rw-r--r-- 1 roger users 82884636 Oct 29 21:44 gcc-4.7.2.tar.bz2
/dev/shm $ rm -rf gcc-4.7.2
/dev/shm $ time tar xf gcc-4.7.2.tar.xz
even on this high-end 3.1Ghz system the .xz version is 3 times faster.
since the tarball is also a good bit smaller (66 vs 82 MB, could be further reduced by using higher compression options), i strongly suggest adding .xz to the official releases, to accommodate for the heavily increased tarball sizes.
before you suggest using the .tar.gz instead:
that one is 100 MB and increases download times and needed storage space significantly.
.xz is the best of both world, fast extraction speeds and small tarballs.
(In reply to comment #1)
> before you suggest using the .tar.gz instead:
> that one is 100 MB and increases download times and needed storage space
> .xz is the best of both world, fast extraction speeds and small tarballs.
I think this has been suggested already, and the people in charge were not opposed to the idea. But... someone needs to step up, and offer themselves to update all the relevant scripts. Best place to offer your help is email@example.com (use a clear subject line, so the people in charge will actually read your email).
>huge 83 MB bzip2
83MB is not huge in any sense.