[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Something like nocompress DEB_BUILD_OPTION


On Fri, 2012-11-09 at 15:52:53 +0100, Bastian Blank wrote:
> On Fri, Nov 09, 2012 at 12:26:19PM +0100, Bastian Blank wrote:
> > | dpkg-deb: building package `linux-image-3.6-trunk-amd64' in `test.gzip.deb'.
> > | dpkg-deb -Zgzip -b debian/linux-image-3.6-trunk-amd64 test.gzip.deb  62.96s user 1.78s system 101% cpu 1:03.77 total
> Some further tests show clearly why this is the case:
> | gzip -c data.tar > /dev/null  6.51s user 0.04s system 99% cpu 6.548 total
> | gzip -9c data.tar > /dev/null  61.46s user 0.08s system 99% cpu 1:01.54 total
> dpkg-deb defaults to -9 for gzip. This mode takes ten times. This all
> for an negligible advantage of 1% smaller package.

There used to be a single global default level (9) for all compressors,
which got changed in 2010 to be backend specific, but only xz and lzma
were reduced to 6. I don't have any problem with changing gzip (to its
upstream default!) if as shown it's a vast improvement speed vs space.

I can certainly do that for dpkg 1.17.x, some more numbers would be
nice though, as in different types of data.tar, for example, but I
would not expect any surprises here, mostly just for reassurance.


Reply to: