Re: [PATCH 7/7] archive: provide builtin .tar.gz filter

[Jeff King <peff@github.com>]

On Thu, Jun 16, 2011 at 11:42:17AM -0700, Junio C Hamano wrote:

> Jeff King <peff@github.com> writes:
> 
> > Also, since it's easy via the external helper route, should there be any
> > other builtin formats? Bzip2? It's not that big a deal for a big hosting
> > site like kernel.org to stick it in their configuration, but I wonder if
> > normal users would find it useful.
> 
> I know k.org statically prepares *.bz2 for any *.gz in /pub/software/
> hierarchy, but isn't bzip2 significantly more expensive (like taking ten
> times as much memory or four times as much CPI time to squeeze the last
> extra 15% out), making it unsuitable for one-shot online use?

I will let J.H. comment on how appropriate that is for k.org; he is the
one who mentioned bzip2 in the first place earlier in the thread.

Even if kernel.org wants it, it is a departure from what we now, though.
People who set up remote upload-archive access long ago and upgrade git
would now suddenly let anyone convince their machines to chew up a lot
of CPU. I don't mind too much doing it for gzip, which takes roughly the
same amount of time as zip, which already exists. Silently adding other
formats may be worse, though.

At the same time, it would be nice for people running git-archive
locally to avoid having to configure a bzip2 filter manually. Maybe
upload-archive should ignore these filters by default, and require a
special config variable to enable them?

-Peff