Indeed. On the egcs snapshot, we save 2M out of 9.5M; it takes 2x as
long as gzip -9, 4x as long as the default gzip (-6 according to the doc.)
I believe it is worth considering this for install kits and possibly
for .deb internals [consider that we could leave the *control* element
gzip'ed, while bzip'ing the data element, in order to provide clean
upgrade warnings -- ie. the old dpkg could still parse the new format
and find the dependency on a new version of dpkg, or something like
that. This is *in addition* to updating the debian-binary tag, I
think...]
bzip2: 263.85user 1.17system 5:14.89elapsed 84%CPU
bzip2 -9: 265.51user 1.36system 5:31.26elapsed 80%CPU
gzip: 82.28user 1.85system 1:51.52elapsed 75%CPU
gzip -9: 133.57user 1.62system 2:44.22elapsed 82%CPU
-rw-r--r-- 1 eichin cygnus 7467838 Aug 27 19:53 egcs-970825.tar.bz
-rw-r--r-- 1 eichin cygnus 7467838 Aug 27 20:15 egcs-970825.tar.bz9
-rw-r--r-- 1 eichin cygnus 9637129 Aug 27 20:01 egcs-970825.tar.gz
-rw-r--r-- 1 eichin cygnus 9566095 Aug 27 20:07 egcs-970825.tar.gz9
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .