On Wed, Nov 19, 2003 at 01:30:50AM +0100, Slaven Rezic wrote:
> > Aha. For some values of tar. That flag is -j on most tars these days.
> >
> > You are in a twisty maze of options, all alike :-(
> >
>
> How compatible is cpio? One could write
>
> cat $tmp | cpio -o -H ustar > $file
I'm not going to trust that people have cpio unless you can show that it
has as wide an install base as tar.
I also don't like trusting -I.
>From the gnutar man page...
COMPATIBILITY
The -y is a FreeBSD localism. The GNU gnutar maintainer has now choosen
-j as the offical bzip2(1) compression option in GNU gnutar 1.13.18 and
later. The -I option is for compatibility with Solaris's gnutar.
The BSD tar which comes with OS X does not appear to have a -I. BSD tar
has nothing like -I.
In short: we're screwed.
About the only thing that's going to be portable is...
system('tar', 'cvf', $file, @list_of_files_to_archive)
which will have all sorts of fun with exec lengths. So you have to break it
up into multiple commands of about 5-10K max each and using -r to append
to the existing archive. Patches welcome.
The other option is to rely on Archive::Tar which is a whole 'nother bag of
worms. Might be the best way to go.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
I know you get this a lot, but you're breathtaking, like a vision of
simplicity
