Re: [Module::Build] codebase? paths in .tar.gz?

[Randy W. S. <Ra...@Th...>]

On 12/21/2003 7:29 AM, Jos I. Boumans wrote:

> 
> On Sun, 21 Dec 2003, [iso-8859-1] Andrew Savige wrote:
> 
>>At the cost of making the A::T code somewhat ugly, I think an imperfect
>>heuristic solution is possible, so that if all PATHs in the tarball were
>>less than 100 characters in length, A::T could write the whole path at
>>the front of the chunk and not use the 'prefix' field -- with a different
>>code path, using the 'prefix' field, followed if any path in the tarball
>>exceeds 100 characters in length.
> 
> i'm very much opposed to this solution, since this still doesn't actually
> /fix/ the problem; it's merely coding around a problem in /other/ tools,
> and it will introduce a very fun /new/ 'bug' that distributions that keep
> their longest path under 100 chars will do the right thing, and any
> distribution with a path > 100 chars will now break... id much rather
> document this shortcoming in other tools and add a dependency on a
> /proper/ tar extractor, that follows the specs for the tar format... A::T,
> gnu tar and quite a few others do... old bsd tars and some )"(#/"#)
> windows tools dont.....
> 
> just my $0.02
> 
> -jos
> 

I don't believe this is the same problem. This is a problem where a tar 
file created on non-windows works but a tar file created on windows does 
not. I uploaded two tar files to:

<http://www.thepierianspring.org/Archive-Tar-1.07.tar>
<http://www.thepierianspring.org/ptar.tar>

Both where created with the old ptar script from ~ 0.23. The first is a 
tar of Archive::Tar 1.07 release from CPAN. A cat shows all the files 
stored as expected but without path info. The second is a copy of the 
ptar script renamed to ptar/ptar.pl. A cat shows the file name as '.pl' 
and no path info.

Randy.

-- 
A little learning is a dang'rous thing;
Drink deep, or taste not the Pierian spring;
There shallow draughts intoxicate the brain;
And drinking largely sobers us again.
                 - Alexander Pope