Re: [Module::Build] Archive::Tar file format

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

On 1/7/2004 4:08 AM, Jos I. Boumans wrote:

> 
> On 7-jan-04, at 3:35, Glenn Linderman wrote:
> 
>> The way I see things, after installing the A::T 1.07 on Windows  
>> (hadn't notice 1.08 yet, Randy has sharp eyes!), I would use M::B to  
>> build a module's .tar.gz and .ppd file, and then there were 3  
>> symptoms, that may or may not be related.
>>
>> 1) During the build of the .tar.gz, warnings were printed about not  
>> being able to add directory entries to the archive.
> 
> by A::T? if so, can you provide me with a test case?

If this is what Glenn reported before, it was fixed in A::T 1.08. From
the README:

-   Fix a bug where adding dirs on win32 gave 'permission denied'

>> 2) Most TAR decoding programs cannot see the PATH data, although the  
>> latest GNU TAR can
> 
> yes, apparently (especially on windows) there's many clients that  
> follow an old(er) spec. Although i am still of the same opinion that  
> these clients are just inherintly broken, I do have a thought on how we  
> may be able to amend this;
> 
> Can one of you who had trouble with the extracting confirm that when  
> extracting this tarball
> 
>     http://search.cpan.org/CPAN/authors/id/K/KA/KAKE/Bot-BasicBot- 
> Pluggable-Module-SimpleBlog-0.02.tar.gz
> 
> everything actually goes as expected, and that a file named
>     
>     Bot-BasicBot-Pluggable-Module-SimpleBlog-0.02/lib/Bot/BasicBot/ 
> Pluggable/Module/SimpleBlog/Store/SQLite.pm
> 
> is living in the extracted directory?

YES! Looks good. I will test more extensively when a snapshot is
available. Thanks.

> If so, we could use the ././@LongLink extended tar format solution,  
> which is
> really meant to be used for paths > 255 chars, but will work equally  
> well for
> our purposes here... i'd equip A::T with a special flag that would  
> trigger the
> use of ././@LongLink files at anything over >100 chars, rather than at  
>  >255,
> thus avoiding the use of the PREFIX header, and thus (hopefully)  
> solving your
> problems :)
> 
>> 3) PPM claims to install the module, but nothing actually gets  
>> installed.  M::B can install the module fine from the source  
>> directory.  Given the other symptoms, it seems like it can't find the  
>> files in the archive, but it reports no errors.
> 
> not much i can do with this one

I believe this might be related to #2 above, but I have not actually
investigated as I don't normally use ppm. When a snapshot of the fixed
A::T is available, I'll check it out and atleast notify someone on the
ppm mailing list if it persists.

Thanks,
Randy.