Hi, I have put together the following srcipt http://www.cs.ait.ac.th/~on/testgtar to help testing exclude patterns in GNU tar. This is a simple Perl script, that should run on any installation; but I
I haven't had a chance to test the script yet, but since I ran across this thread about changes in GNU tar from the Debian developers list <http://lists.debian.org/debian-devel/2006/06/msg01108.html>
Author: Gene Heskett <gene.heskett AT verizon DOT net>
Date: Wed, 19 Jul 2006 08:35:30 -0400
tar-1.19? What happened to 1.16 thru 1.18? Its normally about 3 years per whole point increment... -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' betw
Not sure what I was thinking while I was typing, that should be tar 1.15.91 Frank -- Frank Smith fsmith AT hoovers DOT com Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4
Reading the changelog for GNU tar 1.15.91 is even more frightening, it does not affect only the exclude file, but it does affect the extract command: tar xf foo.tar *.c now means to extract the file
Author: Gene Heskett <gene.heskett AT verizon DOT net>
Date: Thu, 20 Jul 2006 00:35:08 -0400
Yikes! I assume thats been filed as a bug? If not, why not? No guessing about it Olivier. I sometimes wonder why, when a utility such as tar, which can be said to be a mature utility now after what,
Badly ;( However, if I read correctly the old behavior can be restored with the option "--wildcards". Probably the configure script will have to test for version > 1.15.90 and if present add the opti