On Thu, Mar 10, 2005 at 03:05:10PM +0100, Otto Moerbeek wrote:
>
> On Thu, 10 Mar 2005, Bruno Rohee wrote:
>
> > On Thu, Mar 10, 2005 at 10:35:49AM +0100, Dries Schellekens wrote:
> > > Zvezdan Petkovic wrote:
> > > >On Thu, Mar 10, 2005 at 03:29:17AM +0100, Samuel Ljungkvist wrote:
> > > >
> > > >>Since a few friends of mine whined enough about the lack of this feature
> > > >>in OpenBSD tar, I fixed it:
> > > >>
> > > >>http://triplefusion.net/pax-bzip2.patch
> > > >>
> > > >>This does all relevant changes that I can see, including manpages; patch
> > > >>filenames are relative to /usr/src with no directory stripping.
> > > >>
> > > >
> > > >Why would a base system application support an application that is not
> > > >in base system? Wouldn't that be a bug?
> > >
> > > Will bzip2 ever be in the base system? I always tought it had a bad
> > > license (GPL), but this is BSDL (http://sources.redhat.com/bzip2/). So
> > > that is not a problem...
> >
> > There has long been talk of zlib handling bzip2
> > (e.g. http://slashdot.org/article.pl?sid=00/03/10/1043247) but it seems that
> > it is still nowhere, but it would be a great thing for seamless integration
> > with tar...
>
> You are confused. tar/pax does not handle z compression internally via
> zlib. It forks a gzip process to compress or decompress.

Yep, but our gzip is zlib based to if zlib was to handle bzip2 if would
be quite cheap for gzip to handle at least bzip2 decompression then tar.bz2
decompression would be free for tar.

That's quite a few if, I know ;-)

--
We are confronted with insurmountable opportunities.
-- Walt Kelly, "Pogo"