Re: [Bug-tar] GNU tar 1.22 creating USTAR not readable by other TAR implementations

[Tim Kientzle]

Kent Boortz wrote:
> So with the restriction that the "name" field is not to be empty, no
> component of the path can be more than 100 characters,...

No, I'm afraid you're oversimplifying.

The following file can be stored, even though
it has a component of 155 characters:
   ('a' x 155) + '/' + ('b' x 100)

It's just the parent directory of that file
that can't be stored.

In fact, I suggest you modify your test to
explicitly archive just the one entry with the
full path being tested, rather than the parent
directory.  That would avoid some false error
messages from the parent directories:

@@ -90,7 +89,7 @@
         system("echo 'some text' > $path");
       }

-      my $cmd = "$tar -cf $tag.tar $parts[0]";
+      my $cmd = "$tar -cf $tag.tar $path";
 #     print "CMD: $cmd\n";
       my $out = `$cmd 2>&1`;
       my $res = $?;

Cheers,

Tim