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

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

On 12/20/2003 5:23 PM, Jos I. Boumans wrote:
> 
> On Sat, 20 Dec 2003, Ken Williams wrote:
> 
>>On Saturday, December 20, 2003, at 12:17  PM, Randy W. Sims wrote:
>>
>>>Well this atleast proves that the paths are there, thus it is not a
>>>problem with M::B, but I think this is going to be a big issue for
>>>Windows users. I think if it's possible for Archive::Tar to be better
>>>compatible with other tools, it should. If I knew anything about the
>>>tar  format, I'd try to provide a patch. Since I don't, I'll just cc
>>>the maintainer. ;-)
>>
>>I have some kind of vague recollection that maybe this issue in
>>Archive::Tar has been fixed privately by Kane and is just waiting for
>>him to release it.
>>
>>Kane, can you put Glenn out of his misery?  Or am I remembering wrong?
> 
> 
> well, even though m::b may use A::T to build an archive, and ppm uses it
> to extract, it may not be the same A::T -- AS perl ships with a very old
> version of A::T which does not support the full tar standard (including
> the prefix header). Several people have already advised AS to upgrade A::T
> to a recent version, that works on win32 and actually supports most of the
> spec...
> 
> the easiest fix would be to require the client to have a::t > 1.00 to make
> sure this doesn't happen, but i'm not sure how to enforce this...

Hi Jos,

Actually this problem is occuring in recent versions of Archive::Tar; In 
fact, it happens with a post 1.07 snapshot Andrew referred me to a while 
back when we were having other problems (warnings when directories are 
added to the tar). If Ken can confirm that he used 'perl Build dist' to 
create the 'Module-Build-0.21_01.tar.gz' dist currently on CPAN and that 
he used a recent version of Archive::Tar, I think that will narrow down 
the problem to something in the way tar files are created on Windows as 
opposed to other OSs. When I look at that dist in WinZip (one of the 
common programs on windows used to handle tar files), the directory 
structure is there. When I untar that dist and run 'perl Build dist' in 
it, the tar file created on Windows does not show the directory 
structure (although it is there as confirmed by some ported versions of 
gnu tar). So, the problem seems to be in the creation process on Windows...

Regards,
Randy.