All the Perl that's Practical to Extract and Report

Navigation

use Perl Log In

acme (189)

acme (email not shown publicly)http://www.astray.com/Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

So, I started with over a hundred megabytes of tarballs from history.perl.org, and got those down to 6MB of git pack. Once into the Perforce history, I was looking at reducing the ~400MB of Perforce repository even further. After my initial export, it was already something like 250MB of Git pack (I wrote the exporter to make best use of on-the-fly delta compression). I left a fairly aggressive repack on it going, and it took about 30 minutes and left me with these packs [utsl.gen.nz], which are MUCH smaller. The deco

I've long used 7-Zip when I'm forced to use a Windows system, but I've never used it's native 7z format (LZMA).

From a quick scan of Wikipedia it seems that the 7z format is LZMA compression with a 64-bit header and optional extras and the plain lzma tool as described by you here is a raw LZMA compression stream. They are incompatible in that the two tools can't yet process each others files, which is a shame.

I can see lzma files replacing bzip2 files in my archives now. How much smaller could CPAN be ma

Have a look at <a href="http://ck.kolivas.org/apps/lrzip/">lrzip</a> which is a combination of LZMA and rzip. That is, it has a preprocessing stage sorting the data somehow and then does LZMA compression.It doesn't always compress tighter than LZMA but it's usually much faster.