Sven> Upstream authors might choose to release upstream source compressed Sven> by bzip2. So bzip2 compression should be a valid option for source Sven> archives.
Yes, just as another datapoint, GNU Octave does. For the record: miles:/var/spool/mirror/octave [root] # ls -l octave-2.0.11.tar.* -r--r--r-- 1 edd edd 2865036 Mar 25 02:17 octave-2.0.11.tar.bz2 -r--r--r-- 1 edd edd 3625698 Feb 24 17:06 octave-2.0.11.tar.gz which gives a 21 % saving (as the tarball contains over 3000 files). [EMAIL PROTECTED]:~> bc -l bc 1.04 Copyright (C) 1991, 1992, 1993, 1994, 1997 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. (1-2865036/3625698)*100 20.97973962530800965800 quit Sven> IMHO the "pristine" property is more importent than the compression Sven> ratio. If a choice between pristine gzipped and re-compressed bzip2ed Sven> has to be made, I'd vote for the pristine way. Seconded. If space was so important, we would probably not include some of the truly large packages as xbooks and timidity-patches. -- mailto:[EMAIL PROTECTED] According to the latest official figures, http://rosebud.ml.org/~edd 43% of all statistics are totally worthless. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
